On 17.10.2012 21:49, Steve Langasek wrote: > On Wed, Oct 17, 2012 at 11:30:38AM -0700, Christoph Egger wrote: >> Joerg Jaspert <jo...@debian.org> writes: >>> Its for after wheezy, definitely. Also, there are some open issues to >>> be solved for this to happen. The most important is being able to deal >>> with arch all packages. And worse - arch all packages able to build >>> only on certain architectures. But thats outside dak and my area. Goto >>> the buildd/wanna-build people to help for that. > >> Also remeber, there are packages like cmucl that can only be built by the >> same upstream release of itself and can currently survive in Debian >> because the maintainer can upload a bootstrapped binary package along the >> source > > Which is, frankly, an absurd requirement. Someone should fix this package > to bootstrap properly, and if disallowing binary uploads forces the issue, > that's a good thing.
you know better. The last one I did identify is eigenbase-resgen. Others that come to mind are fpc, mlton, ... and adding new features / packages to the GNU toolchain requires manual interaction for glibc/gcc uploads, which can't be done with source only uploads. Matthias -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/507f27a1.2030...@debian.org
