FreeBSD Passes 9000 Ports
Dan writes "Kris Kennaway believes that the french/med port has the honour of being the 9000'th in the FreeBSD ports collection. Congratulations to everyone who has helped to make the Ports Collection such a success over the past 9 years!"
No, what he's saying is that when freeBSD started (Man... I don't even know how long ago), there was less software to put into the port tree, so hitting that "5000+" mark in a year was nearly impossible.
Not Free(as in beer). Free(as in "I'm free to beat you over the head for being a dumbass")
I've been a FreeBSD fan for several years now. Had I been smarter when I was younger, I would have been a fan even longer than that :)
FreeBSD, IMHO, comes pretty darned close to Linux in terms of ease of install and, in many ways, exceeds it in ease of use. Configuration files are where you expect them to be. Utilities are named what you expect them to be named.
And, to tie into this article, the ports collection provides a wealth of great software. There's no issue as to which flavor of Linux you have... if you're running FreeBSD, the port will generally work on your system, whether you compile it from sources or download the precompiled package from one of the ftp mirrors.
Kudos to the FreeBSD team for all their hard work and for giving us such a stable, reliable, useful platform to develop and play on.
Not to take away their thunder, but p5-Unicode-Lite 0.12 counts as a port, so an entire program may have 15 sub-ports. Still, I like it better than Gentoo.
I really hate Dan Patrick.
You do know that portupgrade reads the
Also, I believe they can be put in
And accelerating :)
(Gnu)plot of growth
You can also go to Freshports where you can get a nice view of the cvs-commits to the ports-tree.
Have you tried contacting the maintainer for the relevant autoconf/automake port with your problems in the past ?
cheers,
Rainer
Windows 2000 - from the guys who brought us edlin
hrmmm... > man cvsup ?? Maybe thats just too complicated...
Ports for the TCP/IP protocol. When programs talk to each other, they do so for ports. So when your browser communicates with a web server they go between your address and the server address on port 80 (usually). This is how you prevent network programs from being run on your network. Say you wish to stop kazaa, you close off the ports kazaa can use to communicate. Thus kazaa can't request information from kazaa servers, and servers can't establish a connection to the kazaa client to send it information.