Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-osx
Navigation:
Lists: gentoo-osx: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-osx@g.o
From: Kito <kito@g.o>
Subject: Re: env.d; perl with collision-protect
Date: Fri, 19 Aug 2005 09:45:12 -0500
On Aug 18, 2005, at 5:02 PM, Hasan Khalil wrote:

> The Background:
>
> Perl is almost ready for the default (collision-protect) profiles.  
> I've modified the latest perl ebuild to install all binaries  
> (normally installed to '/usr/bin') into another location (/System/ 
> Library/Perl/${PV}/bin) to avoid collisions. No other collisions  
> are created by the perl ebuild. I'll make these revisions more  
> public once I can get them tested more thoroughly (I already broke  
> Apple's perl on my system, accidentally of course, while working on  
> Gentoo's perl). There are still a few issues to iron out.

This approach only works out of luck, it just so happens the latest  
portage perl isn't the same version as Apples currently shipping  
perl. What happens when/if the next software update decides to  
install Perl 5.8.7? collisions will occur.

Anything that installs to /System is a bad idea IMO, /Library is the  
sandbox apple encourages 3rd party developers to (ab)use.

--Kito

-- 
gentoo-osx@g.o mailing list


Replies:
Re: env.d; perl with collision-protect
-- Hasan Khalil
References:
env.d; perl with collision-protect
-- Hasan Khalil
Navigation:
Lists: gentoo-osx: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Re: env.d; perl with collision-protect
Next by thread:
Re: env.d; perl with collision-protect
Previous by date:
Re: env.d; perl with collision-protect
Next by date:
Re: env.d; perl with collision-protect


Updated Jun 17, 2009

Summary: Archive of the gentoo-osx mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.