[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Perl policy for managing modules ?



-----BEGIN PGP SIGNED MESSAGE-----

Raphael Hertzog, in an immanent manifestation of deity, wrote:
>Darren, if you agree, can you modify the perl package in order to
>install modules in /usr/lib/perl5/debian and make these symlinks ?
>
>- /usr/lib/perl5/$arch/$version => /usr/lib/perl5/debian/$arch
>- /usr/lib/perl5/$version => /usr/lib/perl5/debian

Okay.  That's relatively easy.  I can just change privlib and archlib to 
the directories and put in symlinks.

I do worry about what this might break as well.  Another option would be 
to have /usr/lib/perl5/debian(/$arch)? be the first element of @INC and
leave /usr/lib/perl5/$version(/$arch)? there with only the Perl
installed files.  I'll ask on p5p if this will break things.

Please lets have a decision on this soon.  I've uploaded a new version
of Perl right now to fix the data-dumper problem.

BTW, the reason that this doesn't affect many people on p5p is that
non-core modules are usually installed someplace outside of the Perl
tree.  INSTALLDIRS=perl is usually only used for the core.

>John Lapeyre, in an immanent manifestation of deity, wrote:
>> 	I posted a message on perl5-porters asking for advice.  We need to
>> set a policy quickly, as quite a bit of slink has just become unstable.
>> (Unfortunatley, I was using slink for daily science work. I don't have two
>> machines.)

Sorry about that.  It is called unstable because things break
sometimes.  Even on my development box, I watch debian-bugs to see if
disastrous things happen.  I'm still worried about libc6 2.0.7u-1.

Darren
- -- 
<torin@daft.com> <http://www.daft.com/~torin> <torin@debian.org> <torin@io.com>
Darren Stalder/2608 Second Ave, @282/Seattle, WA 98121-1212/USA/+1-800-921-4996
@ Sysadmin, webweaver, postmaster for hire. C/Perl/CGI/Pilot programmer/tutor @
@		     Make a little hot-tub in your soul.		      @

-----BEGIN PGP SIGNATURE-----
Version: 2.6.3a
Charset: noconv
Comment: Processed by Mailcrypt 3.4, an Emacs/PGP interface

iQCVAwUBNhyGe44wrq++1Ls5AQETHwP/ZyKbtc/4W4AHh+m/7P63wbr2HiJ5Uivq
FtHCkJO7oeMKiDgMTw79PYtkUnKdxj8wsVr8busVav07QXOd7KYA36hfS3A80mi0
i4O9PVv2Akt/h9byFNU31jEMHLe73O00szpCuS28nRkG5wsngMskNtZWJGJOa1/t
FpvwZiTv7go=
=++nM
-----END PGP SIGNATURE-----


Reply to: