# from Ovid
# on Friday 21 December 2007 03:36:

>What we would like, and having it work for both EUMM and
>Module::Build, is to make our installation look like this:
>
>  $ROOT/lib/
>  $ROOT/arch/lib
>  $ROOT/bin/
>  $ROOT/man/man1/
>  $ROOT/man/man3/

1.  Why like that? (vs a more typical tree that you would see in 
e.g. /usr/local where arch is not toplevel)

2.  Have you tried hacking some overrides into Config.pm? (and setting 
a -Ipath & -MConfig for that via PERL5OPT)

3.  What settings are you using to get this far?  What about 
INSTALL_BASE?

I've found prefix & install-dirs (used in combination) to be a bit more 
predictable.  But, I've pondered the idea that maybe just yanking the 
files straight out of blib would possibly be much simpler.

Note:  install-dirs "core" vs "site" will give you fits because it tends 
to get set in the (?:M|B)(?:uild|akefile)\.PL by the dist author.

For further reading:

  http://scratchcomputing.com/svn/stowpan/trunk

Currently, my stow tree has 163 .packlist files, 1562 *.pm files and 
looks like:

  $ cd /usr/local/stow/cpan/; find -maxdepth 3 -type d
  ./bin
  ./lib
  ./lib/perl
  ./lib/perl/5.8.8
  ./lib/perl/5.8
  ./man
  ./man/man1
  ./man/man3
  ./share
  ./share/perl
  ./share/perl/5.8.8

Most of the .ix, .so, and .bs files, and all of the '.packlist's are 
in ./lib/perl/5.8.8/auto though there's this one weirdball:

  $ tree -a /usr/local/stow/cpan/share/perl/5.8.8/auto
  /usr/local/stow/cpan/share/perl/5.8.8/auto
  `-- Compress
      `-- Zlib
          `-- autosplit.ix

Disclaimer:  this was not a 100% fresh install -- some of that was moved 
into here from existing files in /usr/local and there have been some 
snags in stowpan that I haven't had the patience to work-through yet.

Also, this is built on top of a debian Config.pm -- most others are 
bound to be far less workable for stowpan.

--Eric
-- 
"Ignorance more frequently begets confidence than does knowledge."
-- Charles Darwin
---------------------------------------------------
    http://scratchcomputing.com
---------------------------------------------------

Reply via email to