how to make better use of native tools
Hi, I like using macports to get some stuff with lots of dependencies installed. I wonder though why it is neccessary for example to rebuild native tools such as python and perl. Because it tends to cause quite a bit of confusion to have several of those around including severel "site" folders created etc.. Now wouldn't it be possible to have proxy packages such as fink has? I.e. python24- native? It could then be an option. Dunno if macports can handle options like that, but it woul shure be nice. Best Daniel Oberhoff
On 9/15/07, Daniel Oberhoff <daniel@danieloberhoff.de> wrote:
Hi,
I like using macports to get some stuff with lots of dependencies installed. I wonder though why it is neccessary for example to rebuild native tools such as python and perl. Because it tends to cause quite a bit of confusion to have several of those around including severel "site" folders created etc.. Now wouldn't it be possible to have proxy packages such as fink has? I.e. python24- native? It could then be an option. Dunno if macports can handle options like that, but it woul shure be nice.
Interesting idea so long as the versions stay in sync. But the real hit is in the initial compilation of those packages/ports. Disk space is not a big deal anymore, is it? port installed | wc -l 323 du -sh /opt/local 3.4G /opt/local Any porters have any input on this? What breakage might result, if any? -- Paul Beard / www.paulbeard.org/ <paulbeard@gmail.com/paulbeard@mac.com>
Le 07-09-15 à 20:06, paul beard a écrit :
On 9/15/07, Daniel Oberhoff <daniel@danieloberhoff.de> wrote: Hi,
I like using macports to get some stuff with lots of dependencies installed. I wonder though why it is neccessary for example to rebuild native tools such as python and perl. Because it tends to cause quite a bit of confusion to have several of those around including severel "site" folders created etc.. Now wouldn't it be possible to have proxy packages such as fink has? I.e. python24- native? It could then be an option. Dunno if macports can handle options like that, but it woul shure be nice.
Interesting idea so long as the versions stay in sync.
But the real hit is in the initial compilation of those packages/ ports. Disk space is not a big deal anymore, is it? port installed | wc -l 323 du -sh /opt/local 3.4G /opt/local
Any porters have any input on this? What breakage might result, if any?
I tried that for myself a few years ago and it took just one upgrade to break compatibility with OS X provided libxml2 and have me rebuild almost everything. So while the idea may seem attractive, it just does not work. I think fink can handle it because their stable branch moves very slowly and because they have a distinct set of ports for every Major OS version. yves
Am 16.09.2007 um 16:03 schrieb Yves de Champlain:
Le 07-09-15 à 20:06, paul beard a écrit :
On 9/15/07, Daniel Oberhoff <daniel@danieloberhoff.de> wrote: Hi,
I like using macports to get some stuff with lots of dependencies installed. I wonder though why it is neccessary for example to rebuild native tools such as python and perl. Because it tends to cause quite a bit of confusion to have several of those around including severel "site" folders created etc.. Now wouldn't it be possible to have proxy packages such as fink has? I.e. python24- native? It could then be an option. Dunno if macports can handle options like that, but it woul shure be nice.
Interesting idea so long as the versions stay in sync.
But the real hit is in the initial compilation of those packages/ ports. Disk space is not a big deal anymore, is it? port installed | wc -l 323 du -sh /opt/local 3.4G /opt/local
Any porters have any input on this? What breakage might result, if any?
I tried that for myself a few years ago and it took just one upgrade to break compatibility with OS X provided libxml2 and have me rebuild almost everything. So while the idea may seem attractive, it just does not work. I think fink can handle it because their stable branch moves very slowly and because they have a distinct set of ports for every Major OS version.
yves
Ok, but how about tools like python/perl?
Citando Daniel Oberhoff :
Am 16.09.2007 um 16:03 schrieb Yves de Champlain:
I tried that for myself a few years ago and it took just one upgrade to break compatibility with OS X provided libxml2 and have me rebuild almost everything. So while the idea may seem attractive, it just does not work. I think fink can handle it because their stable branch moves very slowly and because they have a distinct set of ports for every Major OS version.
yves
Ok, but how about tools like python/perl?
Programs depending on python or perl often need some specific python libraries that apple does not provide (for example things like py-scientific or p5-mailtools). It is not in macports' culture to install things outside of /opt/local (or /Applications/Macports), so installing these libs require a special libdir that your perl should get. It is easier to count on a fresh install of python to find its own libs than on the user to properly configure apple's python to find libs in /opt/local. Plus apple provided python is version 2.3. Macports provide python2.4 or 2.5 (maybe even python3k) so you have a better more recent with bug fixes implementation and will be less likely to encounter and be enable to correct bugs in that distribution (apple has long provided a buggy ruby while macports' one was working well enough) However, some programs do not require you to install python and work well with apple's one (rubber for example, but I should correct its portfile a little so that it is able to install with python >2.3). Emmanuel
participants (4)
-
Daniel Oberhoff
-
Emmanuel Hainry
-
paul beard
-
Yves de Champlain