Just as a followup to my earlier about how I would have gone about putting up a software development repository I wanted to share with you folks the steps for obtaining the software.
(I run debian testing btw)
Step 1: Fire up konqueror, because it’s my chainsaw application of choice (web browser, ftp client, man browser, info browser, file manager, etc.)
Step 2: In the url, because I don’t know the name of the package I’m looking for type: apt:/search?forge return
Step 3: Wait a few second while the 20,000+ software packages are scanned (Debian is a leviathan among Linux distros for sheer volume of software packaged and ready to go).
Step 4: Look down the list of hits and follow the one called gforge (Here’s how the link for gforge reads:
gforge collaborative development tool - meta-package)
Step 5) Read the description for gforge:
collaborative development tool - meta-package
GForge provides many tools to aid collaboration in a development project, such as bug-tracking, task management, mailing-lists, SCM repository, forums, support request helper, web/FTP hosting, release management, etc. All these services are integrated into one web site and managed through a web interface.
This meta-package installs a complete GForge site.
Step 6) If I was going to install it, I could do either
a) Open a terminal, make myself root, type apt-get install gforge or
b) Run synaptic, the graphical package interface, search for package name gforge, check the install box, press the Apply buton
Wait a few minutes for gforge and all the dependencies to be installed and configured.
Step 7) ???
Step 8) Profit!!!
BTW, for those interested gforge’s immediate dependencies and descriptions are:
gforge-common collaborative development tool - shared files
gforge-db-postgresql collaborative development tool - database (using PostgreSQL)
gforge-dns-bind9 collaborative development tool - DNS management (using Bind9)
gforge-ftp-proftpd collaborative development tool - FTP management (using ProFTPd)
gforge-lists-mailman collaborative development tool - mailing-lists (using Mailman)
gforge-mta-courier collaborative development tool - mail tools (using Courier)
gforge-mta-exim4 collaborative development tool - mail tools (using Exim 4)
gforge-mta-postfix collaborative development tool - mail tools (using Postfix)
gforge-plugin-mediawiki Mediawiki plugin for GForge
gforge-plugin-scmcvs collaborative development tool - CVS plugin
gforge-plugin-scmsvn collaborative development tool - Subversion plugin
gforge-plugins-extra collaborative development tool - extra plugins
gforge-shell-postgresql collaborative development tool - shell accounts (using PostgreSQL)
gforge-web-apache transition package to gforge-web-apache2
gforge-web-apache2 collaborative development tool - web part (using Apache)
After doing that research (about 2 minutes), it simply stuns me again that Microsoft chose to waste its resources on a dead issue. I guess the problem I have is that I keep forgetting that Microsoft doesn’t just provide an operating system for others to develop on, but also software which competes with all other developers on its operating system.
I guess they couldn’t make use of a solution that isn’t one of theirs no matter how easy or how good it is because then they would lose face?