perl and multi-arch (was: Re: Upcoming Debian multiarch support (amd64, sparc64, s390x, mips64) [affects sarge slightly])
- To: Debian Developers <debian-devel@lists.debian.org>, debian-amd64@lists.debian.org
- Subject: perl and multi-arch (was: Re: Upcoming Debian multiarch support (amd64, sparc64, s390x, mips64) [affects sarge slightly])
- From: Anthony DeRobertis <asd@suespammers.org>
- Date: Wed, 14 Jan 2004 02:41:17 -0500
- Message-id: <[🔎] 09EA489B-4665-11D8-A09C-00039317863E@suespammers.org>
- In-reply-to: <20040113162822.GO26745@gwolf.org>
- References: <[🔎] 87k73zynor.fsf@mrvn.homelinux.org> <20040111143747.GE11952@azure.humbug.org.au> <877jzyz6zk.fsf@mrvn.homelinux.org> <1073847077.21793.167.camel@descent.netsplit.com> <87y8sexnvl.fsf@mrvn.homelinux.org> <1073852184.21793.191.camel@descent.netsplit.com> <87ptdqxjqo.fsf@mrvn.homelinux.org> <1073861696.21793.209.camel@descent.netsplit.com> <D41778AC-4518-11D8-A09C-00039317863E@suespammers.org> <87u130me9b.fsf@mrvn.homelinux.org> <20040113162822.GO26745@gwolf.org>
I'm not quite clear on this point. Let's say there is an
architecture-dependent perl library (=modules):
lib-a-perl
First off, what bit-ness do we build this for? 32- or 64-bit? I assume
both. So we have two packages:
lib-a-perl:amd64
lib-a-perl:i386
Now, I package a perl script, foo, which uses a.pm. It is
architecture-independent, so what does it dependency look like? Not
lib-a-perl:amd64 or lib-a-perl:i386. It's the same package on every
architecture, after all.
At first glance, it'd copy the architecture, leaving the rather silly
Depends: lib-a-perl:all. I guess that'd need to be treated specially.
But that leaves the problem that while foo certainly doesn't care which
lib-a-perl it gets, perl certainly does. Well, lib-a-perl:amd64 is
going to depend on perlapi-X and perl:amd64, so I guess that works out
technically.
Does apt deal with that mess nicely? That's a huge dependency tree.
Reply to: