Slashdot Mirror
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
Is a port equivalent to a source package, a binary package, neither, or both ?
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
266 megs / 7001 ports = 0.038 megs per port.
/usr/ports/distfiles/ ? Last I heard the whole ports tree was only about 15MB or so (of Makefiles, patches, descriptions, etc.)... In fact, you can even download a current tarball of the entire ports tree - see www.freebsd.org/ports
.0021MB per port...
Did you clean
So, if it really is 7001 ports, the calculation is 15/7001 =
So what if the FreeBSD ports collection has reached some arbitrary size? Why is this news?
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.
Hmm, Freshports shows 6997 ports as of today. They must be behind a little. Does anyone know the number if you don't count the other languages like russian and japanese ports? It seems that those are mostly repeats of ports already in the collection.
from a clean ports sup -
% wc -l INDEX
7003 INDEX
% du -h ports
109M ports
Your math should contain an operator to model unzipping. So it's more than 15MB unpacked.
~300 MB is a good approximation.
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
One more crippling bombshell hit the already beleaguered *BSD community when IDC confirmed that *BSD market share has dropped yet again, now down to less than a fraction of 1 percent of all servers. Coming on the heels of a recent Netcraft survey which plainly states that *BSD has lost more market share, this news serves to reinforce what we've known all along. *BSD is collapsing in complete disarray, as fittingly exemplified by failing dead last in the recent Sys Admin comprehensive networking test.
You don't need to be a Kreskin to predict *BSD's future. The hand writing is on the wall: *BSD faces a bleak future. In fact there won't be any future at all for *BSD because *BSD is dying. Things are looking very bad for *BSD. As many of us are already aware, *BSD continues to lose market share. Red ink flows like a river of blood.
FreeBSD is the most endangered of them all, having lost 93% of its core developers. The sudden and unpleasant departures of long time FreeBSD developers Jordan Hubbard and Mike Smith only serve to underscore the point more clearly. There can no longer be any doubt: FreeBSD is dying.
Let's keep to the facts and look at the numbers.
OpenBSD leader Theo states that there are 7000 users of OpenBSD. How many users of NetBSD are there? Let's see. The number of OpenBSD versus NetBSD posts on Usenet is roughly in ratio of 5 to 1. Therefore there are about 7000/5 = 1400 NetBSD users. BSD/OS posts on Usenet are about half of the volume of NetBSD posts. Therefore there are about 700 users of BSD/OS. A recent article put FreeBSD at about 80 percent of the *BSD market. Therefore there are (7000+1400+700)*4 = 36400 FreeBSD users. This is consistent with the number of FreeBSD Usenet posts.
Due to the troubles of Walnut Creek, abysmal sales and so on, FreeBSD went out of business and was taken over by BSDI who sell another troubled OS. Now BSDI is also dead, its corpse turned over to yet another charnel house.
All major surveys show that *BS has steadily declined in market share. *BSD is very sick and its long term survival prospects are very dim. If *BSD is to survive at all it will be among OS dilettante dabblers. *BS continues to decay. Nothing short of a miracle could save it at this point in time. For all practical purposes, *BSD is dead.
Fact: *BSD is dying
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 :-)