MacPorts on Linux

[Ben Greenfield]

On Dec 17, 2011, at 3:44 AM, Niels Dettenbach (Syndicat IT&Internet) wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
> 
> 
> 
> 
> 
> Ryan Schmidt <ryandesign at macports.org> schrieb:
> 
>> might be wondering as well, so I'm Cc'ing the mailing list) what made
>> you decide to run MacPorts on Linux. First, I was surprised you
>> succeeded in installing MacPorts on Linux at all; I thought that had
>> broken. But more than that, as you're discovering, a lot of ports and
>> portgroups are written on the assumption that they are running on OS X,
>> or at least Darwin. It will probably take significant effort to remove
>> that assumption, and I'm not convinced it's worth the effort, since
>> MacPorts is, as suggested by its name, made to run on Mac OS X, not on
>> Linux or FreeBSD or other systems. Are none of the existing standard
>> ways of getting software onto a Linux system suitable?
> 
> This would be nice to hear here - i.e. why do you did not used port systems like pkgsrc or Gentoo portage which officially provide linux environments?
> 
> But another point here may be - why MacPorts (which is by principe developed and maintained for Mac OS X only) afaik did not cooperate nor participate on well driven / maintained ports projects like pkgsrc?

It may be surprising to hear that pkgsrc for netbsd was derived from the FreeBSD Ports system which was created by Jordan Hubbard the same person responsible for DarwinPorts/MacPorts.  They are very related and where they don't overlap I believe it is for platform specific reasons. I think that each system, pkgsrc, ports, MacPorts is suppose to manage the platform specific building process while drawing on the large pool of available open source software. I always consider the part of creating a port file as very platform specific part to make use of the posix software out there.
10 years of pkgsrc - pkgsrc and the concepts of package management 1997-2007 (part 1)
Jordan Hubbard - Wikipedia, the free encyclopedia

Thanks,

Ben



> As far as i understand pkgsrc still targets an open list of unixoide / posix operating systems like Linux and BSDs (and afaik even proprietary operating systems) on different hardware platforms. These realizes a potentially large users and developers audience with different operating systems, but at the time no Mac OS X.
> 
> How can MacPorts participate on pkgsrc in the future and how far could that make any sense? From what i understand directly participating directly on pkgsrc could further merge users into larger audiences?
> 
> Maintaining ports for pkgsrc and macports currently are two completely different things and maintaining ports is a huge, ressource consuming job at all. Afaik MacPorts in parts hold ports only available / make sense on Mac OS X, but most ports are even available on other platforms.
> 
> So, does it make sense to i.e. extend pkgsrc towards Mac OS X or making macports in any way more compatible to pkgsrc ports or cooperate with pkgsrc stronger in any other way?
> 
> Pls don't flame if im completely on a wrong way here - i just try to understand the situation.
> 
> 
> cheers,
> 
> 
> Niels.
> 
> - --
> Niels Dettenbach
> Syndicat IT&Internet
> http://www.syndicat.com
> -----BEGIN PGP SIGNATURE-----
> Version: APG v1.0.8
> 
> iIEEAREIAEEFAk7sVlQ6HE5pZWxzIERldHRlbmJhY2ggKFN5bmRpY2F0IElUJklu
> dGVybmV0KSA8bmRAc3luZGljYXQuY29tPgAKCRBU3ERlZRyiDTlkAJ9X9FQSVFrq
> HayUFYVHAQ0BUOvgCQCfZc3RrFZlgL8NY0wAR5q4I6ufFUw=
> =UrVr
> -----END PGP SIGNATURE-----
> 
> _______________________________________________
> macports-users mailing list
> macports-users at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20111217/97b255f6/attachment.html>