Ian Jackson ijack...@chiark.greenend.org.uk writes:
Goswin von Brederlow writes (Re: Multi-arch all-architecture plugins):
As you said these are usualy plugins that nothing depends on. So this
wouldn't help much. Also if there is a dependency than the rules for
m-a:same should be sufficient
Peter Samuelson pe...@p12n.org writes:
[Ian Jackson]
If you install on i386 your 2 binaries and libc6, you /do/ need the
i386 libfakeroot. Otherwise if you say fakeroot your binary it
won't work, no matter that /usr/bin/fakeroot is amd64.
libfakeroot is something of a special case, indeed.
[Goswin von Brederlow]
Except is gimp the only way to use gimp plugins? Isn't there another app
foo that also uses libgimp and its plugins? Then you could have
gimp:amd64, foo:i386.
Actually ... if I remember correctly, gimp plugins are executables, not
libraries, so really they should be
* Peter Samuelson pe...@p12n.org [120214 06:32]:
Package: libpam-fprint
Multi-Arch: same-as libpam0g
Package: gimp-texturize
Multi-Arch: same-as libgimp2.0
Package: libsasl2-modules
Multi-Arch: same-as libsasl2-2
Would this also work with nss plugins? That might be
a bit more complicated
Aron Xu happyaron...@gmail.com:
On Tue, Feb 14, 2012 at 00:09, Ian Jackson
ijack...@chiark.greenend.org.uk wrote:
Goswin von Brederlow writes (Re: Multi-arch all-architecture plugins):
As you said these are usualy plugins that nothing depends on. So this
wouldn't help much. Also
Peter Samuelson writes (Re: Multi-arch all-architecture plugins):
[Ian Jackson]
Where should this fact be declared ? Is it a property of a package
that it makes sense to install it only on all configured architectures
or none ? Or is it a property of the dependency from the depending
On Tue, Feb 14, 2012 at 22:10, Ian Jackson
ijack...@chiark.greenend.org.uk wrote:
Aron Xu happyaron...@gmail.com:
On Tue, Feb 14, 2012 at 00:09, Ian Jackson
ijack...@chiark.greenend.org.uk wrote:
Goswin von Brederlow writes (Re: Multi-arch all-architecture plugins):
As you said
[Ian Jackson]
If you install on i386 your 2 binaries and libc6, you /do/ need the
i386 libfakeroot. Otherwise if you say fakeroot your binary it
won't work, no matter that /usr/bin/fakeroot is amd64.
libfakeroot is something of a special case, indeed. As a hack to my
proposal, perhaps it
Goswin von Brederlow writes (Re: Please test gzip -9n - related to dpkg with
multiarch support):
Steve Langasek vor...@debian.org writes:
the [pam] module packages should be installed
for all archs, not just a subset[1].
Ok, that is acceptable. We just lack any technical means to ensure
Ian Jackson ijack...@chiark.greenend.org.uk writes:
Goswin von Brederlow writes (Re: Please test gzip -9n - related to dpkg with
multiarch support):
Steve Langasek vor...@debian.org writes:
the [pam] module packages should be installed
for all archs, not just a subset[1].
Ok, that is
Goswin von Brederlow writes (Re: Multi-arch all-architecture plugins):
As you said these are usualy plugins that nothing depends on. So this
wouldn't help much. Also if there is a dependency than the rules for
m-a:same should be sufficient. If the package is something to depend
On Tue, Feb 14, 2012 at 00:09, Ian Jackson
ijack...@chiark.greenend.org.uk wrote:
Goswin von Brederlow writes (Re: Multi-arch all-architecture plugins):
As you said these are usualy plugins that nothing depends on. So this
wouldn't help much. Also if there is a dependency than the rules for
m
[Ian Jackson]
Where should this fact be declared ? Is it a property of a package
that it makes sense to install it only on all configured architectures
or none ? Or is it a property of the dependency from the depending
package ?
Neither. If I've configured i386 on an amd64 system just to
13 matches
Mail list logo
