I'm not a port expert but I have an opinion... The problem is this:
the port system exists to give you access to all this wonderful open
source library. Apple likes open source tools but they have no
commitment to interoperability or standards. So if you rely on their
infrastructure, it may chang
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, i
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 <[EMAIL PROTECTED]> 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 n
Le 07-09-15 à 20:06, paul beard a écrit :
On 9/15/07, Daniel Oberhoff <[EMAIL PROTECTED]> 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
On 9/15/07, Daniel Oberhoff <[EMAIL PROTECTED]> 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
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" fo
