Re: Solving the multiarch triplet once and for all

2012-12-18 Thread Julien Cristau
On Thu, Dec 13, 2012 at 11:34:12 +0100, Jakub Wilk wrote: > How about undoing the Python multi-arch mess until someone provides > evidence that the changes solve more problems than they create? > Having some explanation of what's going on would definitely help. Is there a wiki or mailing list ur

Re: Solving the multiarch triplet once and for all

2012-12-18 Thread Barry Warsaw
On Dec 18, 2012, at 02:22 PM, Julien Cristau wrote: >On Thu, Dec 13, 2012 at 11:34:12 +0100, Jakub Wilk wrote: > >> How about undoing the Python multi-arch mess until someone provides >> evidence that the changes solve more problems than they create? >> >Having some explanation of what's going on

Re: Solving the multiarch triplet once and for all

2012-12-18 Thread Andrew Starr-Bochicchio
On Tue, Dec 18, 2012 at 10:24 AM, Barry Warsaw wrote: > On Dec 18, 2012, at 02:22 PM, Julien Cristau wrote: >>Having some explanation of what's going on would definitely help. Is >>there a wiki or mailing list url that I missed and that describes what >>this is about? > > I don't think you missed

Re: Solving the multiarch triplet once and for all

2012-12-18 Thread Jakub Wilk
* Barry Warsaw , 2012-12-18, 10:24: For typical (e.g. C) libraries and headers, you have paths like /usr/lib/ and /usr/include/. Quoting : "If your -dev package contains headers which vary across architectures then it cannot be marked as Multi-

Re: Solving the multiarch triplet once and for all

2012-12-18 Thread Paul Wise
Seems like a lot of effort when there is no /usr/bin//python so there can be only one arch of python installed anyway. What are the use-cases for python multiarch? -- bye, pabs http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of

Re: Solving the multiarch triplet once and for all

2012-12-18 Thread Barry Warsaw
On Dec 18, 2012, at 10:40 AM, Andrew Starr-Bochicchio wrote: >This is the only thing I've come across: > >http://wiki.debian.org/Python/MultiArch Ah, of course. I've added some cross-links. -Barry signature.asc Description: PGP signature

Re: Solving the multiarch triplet once and for all

2012-12-18 Thread Dmitrijs Ledkovs
On 18 December 2012 15:48, Paul Wise wrote: > Seems like a lot of effort when there is no /usr/bin//python > so there can be only one arch of python installed anyway. What are the > use-cases for python multiarch? > cross-compiling the archive / cross-bootstrapping the archive for a new architect

Re: Solving the multiarch triplet once and for all

2012-12-18 Thread Paul Wise
On Wed, Dec 19, 2012 at 12:29 AM, Dmitrijs Ledkovs wrote: > cross-compiling the archive / cross-bootstrapping the archive for a > new architecture. I suppose cross-compiling will be useful but I didn't think python was part of the build-essential set that must be cross-compilable, is that actuall

Re: Solving the multiarch triplet once and for all

2012-12-18 Thread Steve Langasek
On Tue, Dec 18, 2012 at 11:48:56PM +0800, Paul Wise wrote: > Seems like a lot of effort when there is no /usr/bin//python > so there can be only one arch of python installed anyway. What are the > use-cases for python multiarch? Being able to cross-install packages that use libpython; and as Dmitr

Re: Solving the multiarch triplet once and for all

2012-12-18 Thread Wookey
+++ Paul Wise [2012-12-19 01:24 +0800]: > On Wed, Dec 19, 2012 at 12:29 AM, Dmitrijs Ledkovs wrote: > > > cross-compiling the archive / cross-bootstrapping the archive for a > > new architecture. > > I suppose cross-compiling will be useful but I didn't think python was > part of the build-essent

Re: Solving the multiarch triplet once and for all

2012-12-18 Thread Jakub Wilk
* Wookey , 2012-12-18, 17:45: It's not just build-essential that has to be cross-compilable. It's everything you need to build the packages in a debootstrappable (inc build-essential) image. That's actually at least 254 packages. And a quite a lot of those need perl or python to be multiarch