Re: [PATCH] Support :any architecture qualifiers for multiarch
On Wed, Sep 18, 2013 at 14:33:00 -0500, Steve Langasek wrote:
> On Wed, Sep 18, 2013 at 06:24:13PM +0200, Jakub Wilk wrote:
> > Following the “if it didn't happen on a mailing list, it didn't
> > happen”, I repeat here what I said on IRC:
>
> > 12:26 < kwilk> So I rebuilt src:python-aalib, and I ended up these Depends: "python3:any (>= 3.3.2-2~), libaa1".
> > 12:27 < kwilk> This is wrong; the package only works if the interpreter architecture is the same as libaa1 architecture.
> > 12:27 < kwilk> Please revert this ":any" mess.
> > 12:30 < kwilk> In general, just because a script or a module is pure-Python doesn't mean it doesn't care about interpreter's architecture.
> > 12:30 < kwilk> And there's no way to determine automatically whether it cares or not.
>
> Nonsense. It's not in the purview of the script/module to care about the
> architecture of the interpreter.
>
> There are cases for which a package that ships a python script / pure python
> module *does* care about the architecture of the interpreter, but this is
> *not* because of the script / module itself - it's only because of
> architecture-specific python extensions included in the same package, which
> is expressed via a separate arch-specific dependency on libpython; or
> because of restrictions on the architecture-availability of the other python
> modules the package depends on, which should be handled by the package
> manager and *not* hard-coded in the dependencies of the package in question.
>
Well, in Jakub's case the module does dlopen("libaa.so.1"), so while it
doesn't care about the interpreter's architecture, it does need the
libaa1 and python3 packages to be of the same architecture. AIUI
"Depends: python3:any, libaa1" doesn't express that?
Cheers,
Julien
--
Julien Cristau <julien.cristau@logilab.fr>
Logilab http://www.logilab.fr/
Informatique scientifique & gestion de connaissances
Reply to: