On Wed, Feb 10, 1999 at 01:09:43PM +0100, Raphael Hertzog wrote:
> Le Wed, Feb 10, 1999 at 08:55:21AM +0000, Jules Bean écrivait:
> > This seems like a good answer to me.
>
> But not to me. This would mean that i'll have to maintain more than one
> package for a simple perl module.
Or a single multi-binary package..
> Unless we agree to always use the latest perl ...
Use the latest perl for???
> which does mean that renaming perl to perl5.005 is not useful[1].
If you need a specific perl then you use the perl5.005 binary directly,
or the like...
(You also have the perl methods for version handling)
> What I think is that :
> - Debian specific perl module (ie DebianNet.pm, DpkgFtp.pm, others
> modules like that) should go to a non-versionned directories (ie
> /usr/lib/perl5/Debian), and perl should always have this directory
> at the end of @INC.
Why should Debian specific perl modules be any different?
Now, I agree that a non-versioned directory tree for non-binary perl
modules should be considered, but carefully, and I see no reason for
the debian modules to be treated any ..
Also keep in mind that for the system critical ones I would /much/ prefer
have them depend on a old version of perl then risk things trying to use
them with a version of perl which they don't work with, screwing the
system...
> - binary perl module should always use versionned directories.
Agreed..
> - non-binary perl module ? I don't know. Non binary-perl modules can
> also break with perl-thread (ie some are not thread-safe) but I
> don't see this a necessity for a versionned directories.
See above..
They should be considered, but given that it can probably be handled
with one package and a few symlinks, with a minor amount of extra work
on the part of the maintainers of the perl modules, instead of massive
work for everyone involved every time a new, incompatible, perl is
released....
> Over that another problem is that we'll possibly provide perl-thread
> and that binary perl module should be available both for the threaded
> and non-threaded version. But that's not a big problem, perl-thread
> can provide perl5.005-thread and binary perl module for the threaded perl
> can depend on it.
You mean perl5.005-thread can provide perl-thread... (=:]
Just treat it as another perl version..
>
> I'll probably write a script cpan2deb for helping debianizing perl
> modules. This would ease the repackaging of binary perl modules that
> will have to provide threaded and non-threaded binaries.
Sounds good..
Zephaniah E. Hull.
>
> Cheers,
>
> [1] It may help to have both perl on the disk but when the /usr/bin/perl
> link is changed, things stop to work whatever you do. :-(
> --
> Raphaël Hertzog >> 0C4CABF1 >> http://prope.insa-lyon.fr/~rhertzog/
>
>
> --
> To UNSUBSCRIBE, email to debian-devel-request@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
>
--
PGP EA5198D1-Zephaniah E. Hull <warp@whitestar.soark.net>-GPG E65A7801
Keys available at http://whitestar.soark.net/~warp/public_keys.
CCs of replies from mailing lists are encouraged.
Attachment:
pgpOECqT2cuHq.pgp
Description: PGP signature