I could not find the answer anywhere. Why is arch:ppc64 not in the
`any-powerpc` definition ? I would have guessed arch:ppc64 to be very
close to arch:powerpc...
Thanks,
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
do either. any-i386 only includes (linux-)i386,
kfreebsd-i386, hurd-i386, and any future IA32 ports.
(A concrete example of something that would be broken by including ppc64
in any-powerpc: imagine a package that has Architecture: any-i386
any-armel any-powerpc ... because it doesn't care what
On Fri, Sep 12, 2014 at 11:48:26AM +0200, Mathieu Malaterre wrote:
I could not find the answer anywhere. Why is arch:ppc64 not in the
`any-powerpc` definition ? I would have guessed arch:ppc64 to be very
close to arch:powerpc...
any means any OS, not any arches for this hardware
On Fri, Sep 12, 2014 at 12:17 PM, Andrey Rahmatullin w...@debian.org wrote:
On Fri, Sep 12, 2014 at 11:48:26AM +0200, Mathieu Malaterre wrote:
I could not find the answer anywhere. Why is arch:ppc64 not in the
`any-powerpc` definition ? I would have guessed arch:ppc64 to be very
close to
* Mathieu Malaterre ma...@debian.org, 2014-09-12, 14:03:
I could not find the answer anywhere. Why is arch:ppc64 not in the
`any-powerpc` definition ? I would have guessed arch:ppc64 to be very
close to arch:powerpc...
any means any OS, not any arches for this hardware
Hi,
Quoting Simon McVittie (2014-09-12 12:18:35)
There might be situations where it would be useful to have a way to spell
any member of the x86 family, any member of the PowerPC family, any
member of the ARM family and any member of the MIPS family, but we
currently don't.
There is
On Fri, 12 Sep 2014, Jakub Wilk wrote:
Because any-amd64 matches x32. (I kid you not.)
Because any-powerpc matches powerpc.
powerpcspe?
These are probably bugs in dpkg and related tools,
and massively unexpected.
On Fri, 12 Sep 2014, Simon McVittie wrote:
There might be situations where
On Fri, Sep 12, 2014 at 03:11:08PM +0200, Johannes Schauer wrote:
The common fallacy is that the foo in any-foo is the name of a Debian
architecture while in fact it is the name of the CPU which is mapped to one or
more Debian architectures by /usr/share/dpkg/triplettable
Indeed, maybe we need
Hi,
Quoting Andrey Rahmatullin (2014-09-12 18:14:55)
On Fri, Sep 12, 2014 at 03:11:08PM +0200, Johannes Schauer wrote:
The common fallacy is that the foo in any-foo is the name of a Debian
architecture while in fact it is the name of the CPU which is mapped to one
or
more Debian
9 matches
Mail list logo
