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!"

15 of 130 comments (clear)

  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.
  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 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)

  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.
  5. 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 .
  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.

  7. 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...)

  8. 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.
  9. Re:Ports by linimon · · Score: 2, Informative

    You might also want to check out portsman.

  10. 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.

  11. 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.