Cristian Gafton wrote:
>
> On Wed, 30 Jun 1999, Edmund Mergl wrote:
>
> > > Makefile.PL is written, but in general it should go into a general use
> > > perl5 directory, such as /usr/lib/perl5/site_perl, which is anything but
> > > perl version dependant. If it generates paths that are perl version
> > > dependent then the Makefile.PL is busted.
> > >
> >
> >
> > /usr/local/lib/perl5/site_perl/5.005/i686-linux/Pg.pm
>
> You can drop it directly into /usr/local/lib/perl5/site_perl
>
certainly you can, but you shouldn't. On our site we are running
several hundred UNIX workstations including 5 different architectures,
all of them using one NFS mounted /usr/local/lib/perl5 even with
different versions of perl. This works pretty well and relies on the
installation scheme site_perl/arch/version.
If you start dropping modules directly into site_perl you will break
this installation scheme.
> > this is the standard path for all additionally installed modules.
> > It depends on the perl version as well as on the system type.
>
> Nope, this is the standard path for modules that are made to be dependent
> on perl version and architecture.
No, if you do not prepare the Makefile.PL you will get as default the
installation scheme described above. You have to make the module explicitely
independent of architecture and version, but this is not desirable.
>
> Cristian
> --
> ----------------------------------------------------------------------
> Cristian Gafton -- gafton@redhat.com -- Red Hat, Inc.
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> UNIX is user friendly. It's just selective about who its friends are.
--
Edmund Mergl
mailto:E.Mergl@bawue.de
http://www.bawue.de/~mergl