Slashdot Mirror

← Back to Stories (view on slashdot.org)

DarwinPorts Project Crosses 1000 Ports Mark

Posted by pudge on from the that-be-a-heap-load-of-ports dept.

Soroths writes "The DarwinPorts project just achieved a new milestone at crossing the 1000 ports mark in its quest to bring the world of Open Source Software to the Mac OS X platform. Let's give them support and check the main site for more information about the entire project, including how to join!"

3 of 52 comments (clear)

  1. Re:Darwin isn't only for OSX. by T-Punkt · · Score: 4, Interesting
    The NetBSD package system beats that:
    It can be used on Darwin, FreeBSD, IRIX, Linux, NetBSD, OpenBSD and SunOS, see here.


    mk-files for BSDOS and AIX are also present in the tree, so either the documentation is not up to date or support for those systems isn't finished yet.

  2. Re:Darwin isn't only for OSX. by MrChuck · · Score: 4, Interesting
    I have to concur. I've used pkgsrc (netbsd's word for "ports" cause "port" to netbsd means netbsd on a new hardware platform - so same as "port" for free/open users)... where was I? Ah: I've used pkgsrc on NetBSD for years. I'm now using it on Solaris, MacOS X and Linux.

    *WHY* would I want yet another port project?
    What advantage does this one give us? Less filling? Tastes great? better ego fullfillment?

    I'm a long time BSD user (used it on vaxen in the 80s) and as much as I enjoy a rift for the sake of a rift ... can't we stop wasting time doing the same work over and over and perhaps get ONE ports/pkgsrc project going and working well?

    Is there a complelling reason for opendarwin over, say, pkgsrc (which is much more established as a cross platform tool with over 4300 packages done).

  3. Re:Fink (plus advice for fink on 10.3) by SamHill · · Score: 3, Interesting

    Maybe things have changed, but the last time I played with Fink, I got the impression that the developers didn't quite ``get'' Debian, and didn't quite get the BSD ports system, either. The result was kind of clunky and frustrating for people familiar with either inspirational ancestor.

    DarwinPorts, on the other hand, does pretty much what I want it to do without contaminating my OS install. I'd still probably prefer a signed binary package system (if you're just trying something, having to wait for it to both download and build is annoying), but it works well enough for what I've used it for.