Re: Versioned provides ... a necessity !

[Raphael Hertzog <rhertzog@hrnet.fr>]

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. Unless we agree to always use the
latest perl ... which does mean that renaming perl to perl5.005 is not
useful[1]. 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.
- binary perl module should always use versionned directories.
- 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.

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.

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.

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/