Front page | perl.perl5.porters |
Postings from February 2012
On Fri, Feb 03, 2012 at 07:46:49PM +0100, Steffen Mueller wrote: > On 02/02/2012 11:25 AM, Jerome Quelin wrote: > > On 12/02/02 04:02 -0500, David Golden wrote: > >> On Thu, Feb 2, 2012 at 2:47 AM, Todd Rinaldo<toddr@cpanel.net> wrote: > >>> 1. Exclude anything dual life in my perl-core package that will > >>> conflict with a CPAN version. This is mostly bin scripts. > >> > >> Could you elaborate on why .pm files aren't an issue? (Are your RPMs > >> shadowing the core-installed ones?) > > > > because perl already splits @INC to core / vendor / site, in different > > directories (and that's awesome). there's unfortunately only one bin > > directory. :-) > > That depends. With the booking.com's perl builds, there is a site/bin. > Good solution for us, likely rather bad solution for a linux distro. One could solve this by having the "script" installed in /usr/bin be an extremely thin dispatcher wrapper, which looks in a "site/bin", "vendor/bin" and then "core/bin" for the real thing that it wants to exec. One could also use this for something like /usr/bin/perldoc, as a wrapper to call it if found in "core/bin", and otherwise print the OS "localised" help text for "You need to install the [_1] package to use this program." Nicholas ClarkThread Previous | Thread Next