Re: Multiarching perl
Jonathan Nieder <email@example.com> writes:
> Niko Tyni wrote:
>> Yes, it's all to do with that. The perl-base package is Essential:yes,
>> so it needs to stay functional even when its dependencies are not
>> configured. If libperl.so.$VERSION was in a separate package, upgrading
>> either of the libperl package or the perl-base package would
>> potentially break /usr/bin/perl.
> Sure. wouldn't
> libperl-$VERSION-base: ships libperl.so.$VERSION
> perl-base: Pre-Depends: libperl-$VERSION-base
> avoid trouble?
I was going to suggest that too -- it *seems* like it should work. Is the
problem that libperl doesn't always change SONAMEs when making changes
that might break the Perl binary itself (as opposed to external programs
that embed it)? Otherwise, it should be possible to have multiple
co-installable libperl binary packages and have the perl binary itself
pick up whichever one matches, so during upgrades both will be on the
system for a while.
Russ Allbery (firstname.lastname@example.org) <http://www.eyrie.org/~eagle/>