Re: Perl modules and perl upgrade
- To: firstname.lastname@example.org
- Subject: Re: Perl modules and perl upgrade
- From: Chip Salzenberg <email@example.com>
- Date: Thu, 1 Apr 1999 15:39:30 -0500
- Message-id: <19990401153930.D298@perlsupport.com>
- In-reply-to: <19990331071005.B2864@whitestar.soark.net>; from Zephaniah E. Hull on Wed, Mar 31, 1999 at 07:10:05AM -0500
- References: <19990329231958.A7204@k6.resI.insa-lyon.fr> <19990329163013.C931@homey.physics.arizona.edu> <19990330110241.A1227@k6.resI.insa-lyon.fr> <19990330052435.A526@whitestar.soark.net> <19990330204731.A3928@k6.resI.insa-lyon.fr> <19990331071005.B2864@whitestar.soark.net>
According to Zephaniah E. Hull:
> For programs which will work with perl5.004 or 5.005 then they can
> depend on (perl5.004 | perl5.005), but we have no way of knowing if
> they will work with perl5.006, and the upstream perl maintainers
> have proven that they will break things on such 'minor' level version
Um, could you please give an example of such breakage? We've been
extraordinarily careful not to break existing code when updating Perl,
and I'd hate to see our effort be discounted as a failure.
BTW: It might save Debian developers a lot of trouble to have separate
Debian directories for pure Perl modules (no shared libraries) and
Perl extensions (with shared libraries). It's extremely rare for Perl
version updates to break Pure perl code, whereas extensions are likely
to require recompilation at least.
Thus e.g. libwww-perl could live in the pure Perl library directory
and simply depend on "perl5", whereas libdbi-perl would live in the
5.005 extensions directory and depend on "perl5.005".
Chip Salzenberg - a.k.a. - <firstname.lastname@example.org>
"When do you work?" "Whenever I'm not busy."