in reply to Perl module install sub-directories: perl5, site_perl, perl5/site_perl

You seem to make the premisse that everyone has such a directory set up. I have: 
    /opt/perl/lib/5.8.0
    /opt/perl/lib/5.8.0/auto
    /opt/perl/lib/5.8.0/i686-linux-64int-ld
    /opt/perl/lib/5.8.0/i686-linux-64int-ld/auto
    /opt/perl/lib/site_perl/5.8.0
    /opt/perl/lib/site_perl/5.8.0/auto
    /opt/perl/lib/site_perl/5.8.0/i686-linux-64int-ld
    /opt/perl/lib/site_perl/5.8.0/i686-linux-64int-ld/auto

[download]

I've installed Perl many, many times, and I do not recall seeing such a setup as yours.

Abigail

  • Comment on Re: Perl module install sub-directories: perl5, site_perl, perl5/site_perl
  • Download Code

Replies are listed 'Best First'.
Re: Re: Perl module install sub-directories: perl5, site_perl, perl5/site_perl
by kilinrax (Deacon) on May 09, 2003 at 23:21 UTC

    Which does beg the question; what is different about my setup to cause this?

    Even if I'm an abnormality in having a 'perl5' directory, you have 'site_perl' - which I've yet to discover an explanation for the existence of.

    Is there any reason all modules can't live in $PREFIX[/$REVISION][/$ARCH][/auto] ?

[reply]
      There may be other settings that also affect directory structure, but the 2 most familiar to me are as follows (http://search.cpan.org/src/JHI/perl-5.8.0/win32/Makefile): 
      #
# Comment this out if you DON'T want your perl installation to be vers
+ioned.
# This means that the new installation will overwrite any files from t
+he
# old installation at the same INST_TOP location.  Leaving it enabled 
+is
# the safest route, as perl adds the extra version directory to all th
+e
# locations it installs files to.  If you disable it, an alternative
# versioned installation can be obtained by setting INST_TOP above to 
+a
# path that includes an arbitrary version string.
#
#INST_VER = \5.8.0

#
# Comment this out if you DON'T want your perl installation to have
# architecture specific components.  This means that architecture-
# specific files will be installed along with the architecture-neutral
# files.  Leaving it enabled is safer and more flexible, in case you
# want to build multiple flavors of perl and install them together in
# the same location.  Commenting it out gives you a simpler
# installation that is easier to understand for beginners.
#
#INST_ARCH = \$(ARCHNAME

      [download]

      MJD says you can't just make shit up and expect the computer to know what you mean, retardo!
      I run a Win32 PPM repository for perl 5.6x+5.8x. I take requests.
      ** The Third rule of perl club is a statement of fact: pod is sexy.

[reply]
[d/l]
      You have site_perl as well. At least, you listed it. site_perl is where all your locally installed modules go, that is, all the modules that aren't part of the standard distribution. Just like that (Unix) systems have /usr and /usr/local.

      Abigail

[reply]
        That makes a lot of sense. I thought it might be something like installed by hand / installed with CPAN (though not that specifically, as I install everything with CPAN). Core vs non-core hadn't occurred to me. Thanks :)
[reply]

In Section Seekers of Perl Wisdom