FreeBSD Ports Collection Reaches 7000
An Anonymous Coward writes: "The FreeBSD ports collection has just had the 7000th port committed.
The original message can be read in Kris Kennaway's post to freebsd-ports."
← Back to Stories (view on slashdot.org)
FreeBSD is catching up fast. Hopefully soon we'll have two spectacularly complete UNIX distributions to choose from!
Imagine how many it could be if it wouldn't take so darn long until ports made by non-commiters make it in CVS. There are a lot of open "New Port:" pr's in GNATS, and I strongly doubt that they are all problematic in any way, problably nobody found the time to look at them in most cases. This is quite annoying, if you created a port and it sits there uncommited for months.
However, congrats to all porters! Keep on the good work.
Programming can be fun again. Film at 11.
Dear Clue4All:
...
Curious about your sig, and where your figure of less than 3% comes from. Do you have a program which actually sorts / categorizes the software on your machine by license? That sounds like an interesting statistic, I wonder what various populations's result curves would look like in that case
timothy
jrnl: http://tinyurl.com/c2l8yr / foes: http://tinyurl.com/ckjno5
a port is the source, with freebsd specific diffs, that gets patched and then compiled.
Common sense is not so common.
okay, first I'll explain how ports work... then I'll tell show you that your numbers are wrong.
/usr/ports# find . -type d -maxdepth 1 -ls
/usr/ports# find . -type d -maxdepth 2 | wc -l
/usr/ports# du -h
to download new ports you use cvs. they're broken down into categories. www, ftp, sysutils, audio, etc. when you run your cvs script, it will always download files called: Makefile, distinfo, pkg-comment, pkg-descr, and pkg-plist. Occasionally it will create a "files" directory and include patches. It always downloads the patches, because they're generally small anyways.
Just to have exact figures I downloaded all of the ports while writing this (I usually don't download ports having to do with japanese, chinese, etc.)
Here's what I found:
returns 54 directories, one is "." and four don't count. (they're used by FreeBSD)
returns 7111 results. Now we need to subtract the 55 "."'s and all of those "."'s have a "." of their own.
7111 results, minus 110 = 7001 total ports.
returns 266 megs.
266 megs / 7001 ports = 0.038 megs per port.
Common sense is not so common.
find
still have to remove BSD special ones from this
and a package is the binary version....so you can
do:
make package
which will compile and install the port (from source) and also create a binary package you can then add to your other machines.....Hoo Har!
If you are at a slow internet connection you cannot afford to download all the sources.
I think this is the main flaw of the ports system and the reason why *BSD is not used of stand alone desktops very often.
Yes, I know that there are binary packages out there now.
BTW: a search in the posts package for "bsd is dying" returns "Sorry, nothing found. You may look for other FreeBSD Search Services."
It seems that there is still much to do for them.
Owner of a Mensa membership card.
Ports schmorts, don't be girly grab the source and compile. If it doesn't work it's not worth trying.
Anyways, who's going to count them all to make sure no-one's telling fibs?
The Final Word
It's news for the exact same reason that the release of Linux-development kernel gazillion-and-one is slashdot Frontpage News.
I suspect you are trolling. but...
/usr/share/doc to /usr/doc. Until every distro, and every Unix-like OS is identical this will be the case.
Two many people know how to write code, but don't know how to develope code. A symptom of this problem is that you get code that was written on a Linux platform, but was not written or designed for a Unix platform. So yes there is lots of unportable code.
The need for a ports system would exist regardless of the "quality of free software." Perfectly portable code will always require some patching to configure the software for the target OS. Even if all the patch does is move the location of the documents from
damn, even after a preview:
s/Two/Too/
The way I counted them was by building a new INDEX file (one entry per port) and then running wc -l on it :-)