On Sun, Oct 09, 2011 at 09:46:02PM +0200, Reinhard Tartler wrote: > On So, Okt 09, 2011 at 21:05:56 (CEST), Jurij Smakov wrote: > > > I thought about it, and I don't really see why we would keep the > > linux32 wrapper on the buildds. It made sense in the past, when we > > supported sparc32 and really wanted to guarantee that if a package > > has CPU type autodetection, we would get the code which works on both > > sparc32 and sparc64 machines. These days it probably just leads to a > > ton of unnecessarily-unoptimized binaries in the archive. > > Indeed, please notify me (e.g., with a wishlist bugreport) when the > buildds get changed, because I have to revert this change then:
I basicly have 2 questions: - Do all sparc porters agree that I should drop the linux32 from the buildds? And will people fix things if it breaks? - Do you still plan to have a (full) release of sparc for wheezy, or will you try to move to sparc64? Kurt -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
