Slashdot Mirror


FreeBSD Ports Collection Breaks 10,000 Ports

sremick writes "After breaking the 9,000 mark in July, the FreeBSD ports collection was well on its way of crossing 10,000 by the end of 2003. Sure enough, we made it! According to freshports, the number of ports in the FreeBSD ports tree currently stands at 10,015. This little graph is also nice, though not completely current. Way to go, FreeBSD!"

130 comments

  1. The title by aridhol · · Score: 4, Insightful

    That title makes it look like changes to the port system broke all the ports. Maybe "exceeds" rather than "breaks"?

    --
    I can't say that I don't give a fuck. I've just run out of fuck to give.
    1. Re:The title by sremick · · Score: 1

      Yeah I thought about that after. Oh well. I can't fix it myself. Maybe someone else can? Regardless, it's true even if it can be misinterpreted, and the proper meaning becomes apparent immediately in the first sentence... you don't even have to RTFA. ;) (WA?)

      But if a mod wants to tweak the title, I won't be offended.

    2. Re:The title by evilviper · · Score: 1

      Yes, I've had more than one occasion when it seemed like 10,000 ports broke for me...

      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
    3. Re:The title by Anonymous Coward · · Score: 0

      Yeah, the title reminded me of the kind of complaint you'd see on freebsd-current or -ports.

    4. Re:The title by hmallett · · Score: 1

      As I write, freshports says that there are 10022 ports. However, 62 of those are marked as broken, and 4 are marked as forbidden, so perhaps the celebration is premature. Only 44 ports need to be fixed!

    5. Re:The title by OrangeSpyderMan · · Score: 1

      Yes, but Slashdot has these things called editors. Now if they can't edit badly written items into sensible english, they're not editors but news monkeys.

      --
      Try NetBSD... safe,straightforward,useful.
    6. Re:The title by endx7 · · Score: 1

      As I write, freshports says that there are 10022 ports. However, 62 of those are marked as broken, and 4 are marked as forbidden, so perhaps the celebration is premature. Only 44 ports need to be fixed!

      Actually, it isn't that bad. Some ports report they are broken based on versions (like version of fbsd, perl, etc). For example, take a look at the Makefile of gnump3d. It requires a certain version of perl before it'll be 'unbroken'. Then again, it may be worse, because some don't compile, but aren't labeled as BROKEN. bento is a great place to find out which ports compile and which don't.

    7. Re:The title by stevey · · Score: 1

      Interesting; I assumed that any modern version of Perl would work for my gnump3d app.

      I've not touched it since the Savannah.gnu.org compromise, but I'll have a look over the code and try to test it on a BSD box sometime soon.

  2. Just wait... by zulux · · Score: 3, Funny



    I hear a port of apt-get is in the works!!!!!

    (kidding)

    --

    Moneyed corporations, non-working 'poor' and criminal prisoners are turning productive citizens into tax-slaves.

    1. Re:Just wait... by BrookHarty · · Score: 2, Interesting

      I'm wondering how the work on merging FreeBSD Ports, Gentoo portage and Fink is coming along. There was an announcement that the groups where working on a Centeralized port systems (Together). 1 ports for every paltform. Then you could apt-get, emerge, pkgadd, rpm, whatever...

      The saved man hours in a centeralized ports system would be amazing.

    2. Re:Just wait... by TheRaven64 · · Score: 4, Interesting
      The saved man hours in a centeralized ports system would be amazing.

      Even more man-hours would be saved if people wrote in ISO C using only POSIX functionality, without littering their code with Linux-isms, or worse still distribution-specific things. Creating a package is relatively easy once you can make the code compile.

      For something done right, look at Psi. The same code builds on Linux, *BSD, Solaris, Windows and Mac. When the first Mac version was released, none of the developers even had a Mac (they just compiled it on someone else's machine). This is possible by coding to cross-platform APIs (in the case of Psi, the only dependency is Qt, which runs almost anywhere).

      --
      I am TheRaven on Soylent News
    3. Re:Just wait... by noselasd · · Score: 1

      So, one should not write GUI apps ? afaik posix doesn't standarize a GUI.
      There is Motif in the SUS specification though..

    4. Re:Just wait... by Anonymous Coward · · Score: 1, Insightful

      Your suggestion is as useful as suggesting that everyone standardise on a single Unix or a single distribution of Linux. Or a single editor.

      > Even more man-hours would be saved if people wrote
      > in ISO C using only POSIX functionality, without littering
      > their code with Linux-isms, or worse still
      > distribution-specific things. Creating a package is
      > relatively easy once you can make the code compile.
      >
      But wait, POSIX is considered by *some* to be *broken* such as the threads model, handling of locking and the non-existence of asprintf(3) which I believe orginated in OpenBSD and is now available from all of the Freeix, but not Solaris.

      Okay, easy, so let's choose a standard. Oh, picking at random <flame suit=on>How about everyone choose Red Hat Linux 9.0 with patches as of 20030318</flame>. Oh, 99% of developers don't like *that* too much, gee that's a surprise. Alternatively, let's stay permanently in the 1980s or establish a working group that can wrangle for years before making a decision.

      There are some very useful functionality which is genuinely operating system-specific (see Linux capabilities). Other things like PAM would have been delayed/hindered if one was forced to implement it on 5 operating systems at once (Solaris, Linux, *BSD). Finally, purely technical differences of opinion will occur, software development is often a game of trade-offs.

      Certainly, one should *try* to develop most of the code using POSIX only. In turn libc and kernel developers should think hard before introducing *another* syscall or library call. But OS-dependences will happen, it's the real-world. Deal with it. Any ports model will also have to take that into account.

    5. Re:Just wait... by /dev/trash · · Score: 1

      I can't wait til emerge gets ported.

      Oh wait.

    6. Re:Just wait... by jschauma · · Score: 1

      While it's not the merger of FreeBSD Ports, portage and fink, NetBSD's Packages Collection aka pkgsrc supports a large number of different operating systems (NetBSD, Darwin, FreeBSD, Irix, Linux, OpenBSD, Solaris), with support for more platforms (BSD/OS, HP-UX, AIX) in the works. Full Documentation here.

      --

      -- "Tradition is the illusion of permanence."
    7. Re:Just wait... by stripes · · Score: 2, Interesting
      Even more man-hours would be saved if people wrote in ISO C using only POSIX functionality, without littering their code with Linux-isms, or worse still distribution-specific things. Creating a package is relatively easy once you can make the code compile.

      If people only used the "standard" interfaces then the 'void' extention to K&R would never have gotten enough widespread use to be included in ANSI. Nobody would use the better select-like interfaces (epoll, kqueue) and we would never find out which should be included as a "standard" next time around. Oh, and no threads. And more buffer overuns because strlcpy won't be used just strncpy (which gets misapplied and allows buffer overuns more offen then not due to poor interfaces).

      The people that push the envlope are the ones that influance the next standards.

      (That's not to say one should go use sendfile/splice when you have no need, but if you need the performance, don't shy away)

    8. Re:Just wait... by Anonymous Coward · · Score: 0

      Even more man-hours would be saved if people wrote in ISO C using only POSIX functionality...

      Probably not, actually. That would save time porting code, but forcing everyone to use one language, instead of actually choosing the right tool for each job, would lead to many more hours being wasted.

      For something done right, look at Psi. The same code builds on Linux, *BSD, Solaris, Windows and Mac . . . (in the case of Psi, the only dependency is Qt, which runs almost anywhere)

      Except that Qt doesn't have a mature free Windows version. Whoops, bad example methinks.

  3. Holy crap!!! by Anonymous Coward · · Score: 2, Funny

    I thought they meant 10,000 ports won't compile any more!! Find the guy that checked in *that* change and SHOOT HIM!

    But, uh, that's not what it means. So congrats guys, I LOVES ME THE FREEBSD PORTS!!!

  4. Timeline Summary by MBCook · · Score: 4, Insightful
    Timeline summary:

    Time to reach 1000 ports: 30 Months
    Time to reach 2000 ports: 18 Months
    Time to reach 3000 ports: 12 Months
    Time to reach 4000 ports: 10 Months
    Time to reach 5000 ports: 6 Months
    Time to reach 6000 ports: 6 Months
    Time to reach 7000 ports: 6 Months
    Time to reach 8000 ports: 6 Months
    Time to reach 9000 ports: 6 Months
    Time to reach 10000 ports: 6 Months

    Seems development has been rather steady for a while now. I predict 11,000 ports in... 6 months.

    --
    Comment forecast: Bits of genius surrounded by a sea of mediocrity.
    1. Re:Timeline Summary by Anonymous Coward · · Score: 0

      Timeline summary: Time to reach 1000 ports: 30 Months Time to reach 2000 ports: 18 Months Time to reach 3000 ports: 12 Months Time to reach 4000 ports: 10 Months Time to reach 5000 ports: 6 Months Time to reach 6000 ports: 6 Months Time to reach 7000 ports: 6 Months Time to reach 8000 ports: 6 Months Time to reach 9000 ports: 6 Months Time to reach 10000 ports: 6 Months I predict *BSD will die in 1 month.

  5. Ports by Quill_28 · · Score: 1

    Is there a good listing of all the ports and what they do?

    I know a script could be written to search /usr/ports/ and cat the pkg-descr file, but is there anything out there a little more user-friendly?

    1. Re:Ports by kernelistic · · Score: 5, Informative
      Here's a good start...
      cd /usr/ports
      make readmes
      You'll want to go grab a sandwhich at this point while it goes through all of the ports and creates their associated readme files. You'll then be able to use your favorite browser to list the ports and their descriptions. The URL you want file:///usr/ports/README.html .
    2. Re:Ports by no_l0gic · · Score: 4, Informative

      My favorite FreeBSD ports related reference:
      http://www.freshports.org/

      News of new/updated ports as well as a searchable index of all ports (and you can navigate the site the same as your ports directory structure).

      Also, on a somewhat related note, you know of the `cd /usr/ports && make search name=blah` or key=blah feature, right?

      Happy New Year! (give or take a TimeZone...)

    3. Re:Ports by Anonymous Coward · · Score: 0
    4. Re:Ports by xA40D · · Score: 2, Informative

      Is there a good listing of all the ports and what they do?

      /usr/ports/INDEX

      I know a script could be written to search /usr/ports/ and cat the pkg-descr file, but is there anything out there a little more user-friendly?

      cd /usr/ports/
      make search key=foo

      Or, in answer to both your questions, try the FreeBSD website

      --
      Do you mind, your karma has just run over my dogma.
    5. Re:Ports by Anonymous Coward · · Score: 0

      I believe there is a graphical (KDE I believe) tool for searching and maintaing copies of ports. It's under sysutils and begins with a b. I don't rememebr what exactly it is called. Bruce perhaps? Anyway, it is easy enough to find and easy to use. It is a KDE app and about as user-friendly as you will find for browsing the ports tree.

      Brandon

    6. Re:Ports by linimon · · Score: 1

      barry. I don't know if it's really current, or just a nice start.

    7. Re:Ports by linimon · · Score: 2, Informative

      You might also want to check out portsman.

    8. Re:Ports by Anonymous Coward · · Score: 0

      Try http://www.freebsd.org/ports
      or make search key={keyword}
      or make search name={name}

      On-lamp also has some useful articles:
      http://www.onlamp.com/pub/a/bsd/2003/09 /18/FreeBSD _Basics.html
      http://www.onlamp.com/pub/a/bsd/2003 /08/28/FreeBSD _Basics.html
      http://www.onlamp.com/pub/a/bsd/2003 /08/07/FreeBSD _Basics.html

    9. Re:Ports by Jerk+City+Troll · · Score: 1, Troll

      $ lynx /usr/ports/<branch>/<package>/README.html

      I know, monumentally complicated.

    10. Re:Ports by Anonymous Coward · · Score: 0

      Check out /usr/ports/INDEX

    11. Re:Ports by Quill_28 · · Score: 1

      Well you understand it so I'll assume you are being sarcastic.

      Don't complain about being unfairly modded down when you are a jerk to modders.

  6. 10,000 ports... by cperciva · · Score: 4, Interesting

    ... and three of them are mine.

    Makes one realize how insignificant one's own contribution is, when one has contributed less than 0.03% of the total.

    1. Re:10,000 ports... by MikeX · · Score: 2, Insightful

      Yea, but if you factor in my 0 ports, then your 0.03% is comparably astronomical.

    2. Re:10,000 ports... by geniusj · · Score: 1

      I only have two myself. I do wonder who has the most. I know someone who has quite a few though:

      > find /usr/ports -name "Makefile" -exec egrep "MAINTAINER=[[:space:]]*knu@" {} \; | wc -l
      313

  7. Re:FreeBSD is dying by kjd · · Score: 1, Funny

    If you strike it down, it will become more powerful than you can possibly imagine!

  8. heh. by pb · · Score: 1

    Way to go, guys; the comparative newcomer that I use (Gentoo) is only up to 7,167 or so packages!

    --
    pb Reply or e-mail; don't vaguely moderate.
    1. Re:heh. by Anonymous Coward · · Score: 0

      s/gentoo/BSD/;

  9. Re:I'm glad BSD is dying... by sparklingfruit · · Score: 0, Troll

    Not one to feed the trolls, but they need to be countered once in a while.

    BSD is not dying, BSD is not a "terminal OS". BSD is fast, stable, scalable and rivals Linux in areas of security (especially openBSD) and openness. It's a good middle ground for developers worried about the implications of the GPL and has it's advantages as well as disadvantages.

    BSD and Linux both have their place in the Open Source world, and neither will be leaving us any time soon.

  10. Re:The End of the road for BSD by bsd_usr · · Score: 0, Troll

    Would you like to list which these are? Also, how many of the 10,000 or so ports would you consider to be most?

    Seems like there's only like 64 ports that are considered broken. Either you have some fucked up logic, but 64 out of 10,019 doesn't sound like most to me.

    Congrats to the FreeBSD. Keep up the good work! You're doing great!

  11. Re:My personal experience in the FreeBSD world by linimon · · Score: 0, Offtopic

    Hey Harv, apparently the moderators haven't had a chance to notice that this is one of your usual reposts to all *BSD threads. That's the only way this post could still be labeled 'interesting'.

  12. Re:The End of the road for BSD by linimon · · Score: 1

    Harv, this is factually incorrect as per my last reply to one of your threads. There are 237 broken on i386-current, about half due to gcc3.3 issues.

  13. pb: Not 7167 by Halanegri · · Score: 1

    This is how you determine the amount of packages in Portage: # qpkg | wc -l 5930 ;) btw, "emerge gentoolkit" to get qpkg.

    1. Re:pb: Not 7167 by Halanegri · · Score: 1
      erm, sorry about that, newlines didn't make it in, 'twas my first reply to /.

      Anyway, it should be:

      # qpkg | wc -l

    2. Re:pb: Not 7167 by Anonymous Coward · · Score: 0

      qpkg | wc -l
      6273

  14. Re:How many ports are nessary? by AndyElf · · Score: 1

    $ ls /var/db/pkg|wc -l
    334

    but that's on a recently re-installed box, I think I used to be up in 500+

    --

    --AP
  15. Re:YHBT YHL HAND by Anonymous Coward · · Score: 0

    Was tried a year ago. Did not work then.

    Proof? I've never seen an example of the *BSD community ever ignoring troll posts, or being able to shut its mouth from trolling in Linux threads for that matter.

  16. Re:How many ports are nessary? by sremick · · Score: 2, Interesting
    427 here. Keep in-mind that's not necessarily 427 applications I have icons for or that are on my menus. Ports includes dependencies such as libraries and other obscure things. This allows version control, dependency control and proper maintenance for everything installed outside of the base OS.

    In fact, everything on my system is either part of the base or was installed via ports. This includes perl CPAN modules, which have their own entries in the ports tree.

    Freshports' categories list is a great way to browse the contents of the FreeBSD ports tree.

  17. IPTraf still too difficult or something? by azaze1 · · Score: 1
    And yet with 10,015 ports, they STILL don't have the best live traffic monitor from linux... IPTraf.

    The alternatives for freebsd are just garbage in comparison. ifstat is as bland as it gets. trafshow comes close in a few respects but still doesn't touch IPtraf. Where is the "Lan Station Monitor", where are the detailed interface statistics?

    Ntop is not an option, its a for browsers, not the console.

    So many ports, so many contributors, it must be a conscious effort to avoid porting this program. Is it that difficult? Yes I know it relies too heavily on linux's /proc to get its data. So its not a project that takes 5 minutes to port to freebsd. Does that mean its not worth doing?

    I'm not a programmer and I don't wish to become one. I just hope that some day, at some point someone decides to port this. Afterall there is a ton of garbage in ports right now, it'd be nice to add some *new* AND *useful* tools.

    1. Re:IPTraf still too difficult or something? by bark · · Score: 1

      would MRTG do everything that iptraf does? i'm thinking that iptraf might be wedded too closely to the linux net implementation .. maybe that's why it hasn't been ported. it's probably not worth porting, but it's worth rewriting to fit the bsd platform. porting sometimes just gets damned hard ... hard enough that rewriting is simple by comparison.

    2. Re:IPTraf still too difficult or something? by azaze1 · · Score: 1

      mrtg would not come close. For one you need a browser to look at the graphs. And unless your poll time was every second, it wouldn't accomplish the same things. As for porting vs rewriting, maybe it would be easier to rewrite it. If you have access to a linux box, run iptraf on it, look at the lan station monitor, pick the interface. Then try and come up with a solution on par with that for viewing real-time LAN traffic. Who is using what bandwidth at that very moment in time. ("who" could be whatever name you associate with the mac address).

    3. Re:IPTraf still too difficult or something? by TwistedSquare · · Score: 1

      Heh-heh just emerged that, its good fun to watch as the IP traffic for my SSH line running iptraf flies up with each update.

  18. IPTraf still too fubar'd. by mrplastik · · Score: 1

    This stems from the author's inability (or he just plain doesn't care) to write cross-platform conforming code. /STOP/ using linux headers in your code, and join the world of ANSI C already. Don't blame *BSD, or shall I begin a tirade about Linux because none of my audio applications written for Windows work in it? Makes just as much sense.

    quote> it'd be nice to add some *new* AND *useful* tools.

    You don't have to rely on ports to install stuff, I have to compile stuff manually quite often, ports is more of a "nicety". Might I also add, it's VERY common for me to have to FIX someone's code so it compiles on platforms other than Linux. (So much for skilled ... programmers) If ports is full of crap, that'd be the "open source" community's fault for releasing shoddy/worthless code. The ports commiters just make it simplistic to compile with dependancies, they (usually) didn't write the stuff. Your post sounds more like trolling than a legitimate cry for help/suggestions.

    (use nload if you're looking to see real-time traffic utilization on your console, including a nifty real-time ascii graph, and a gob of other configurable stuff - ooh-aah.)

    -mpf

    1. Re:IPTraf still too fubar'd. by azaze1 · · Score: 1

      Good insight about why it hasn't been ported, thanks. But for the record I'm no troll. I rarely post at all and I enjoy both linux and *bsd.

    2. Re:IPTraf still too fubar'd. by mrplastik · · Score: 1

      My mistake. There's been almost nothing but trolling going on in these threads, so I suppose I've got an itchy trigger finger at times. ;)

      -mpf

  19. Re:FreeBSD is dying ... *chuckle* by mrplastik · · Score: 2, Insightful

    Ah, the shameless trolling.
    I'll humor you, and let's JUST say, (Although, I certainly disagree with your premise however.) FreeBSD is dying. What would your point be? It's still better than Linux, in more aspects than I have time to list here. Besides, The -core team won't evaporate, our community is too large, and too many skilled coders would love a commit bit.

    (I've been running linux since kernel 0.99, and freebsd since kernel 2.2, I've got some clues about both os's, as I've hacked around in both kernels extensively too)

    Well, going along with your logic, I guess Linux is dying too, since Microsoft still holds so much market share, and will continue to. Had you happened to notice the climb in w2k3 servers? It'd still be a POS no matter if 99% of Internet/Intranet Servers ran it. According to you, the open source community has quite a grim future.

    I suppose you draw your conclusions differently,however I don't implement an operating system because it's the "hip" thing to do, or because of a "clique". Nor because, "everyone else does" - I run FreeBSD at every one of our locations, because I live and die based on how well my servers operate, and for the last ~10 years or so, I've been QUITE content thanks to FreeBSD. (There was a time I was quite content with Linux as well, that ended not long after the 2.0 kernel came on the scene, fyi.)

    Fact: Clueless is as clueless does.

    -mpf p.s. don't forget, freebsd existed when it's user-base was not even 1/1000th of what it is today.

  20. Re:FreeBSD is dying ... *chuckle* by Anonymous Coward · · Score: 0

    YBHT. YHL. HAND.