On Sat, Oct 25, 2014 at 11:15:23PM +0200, Laurent Bigonville wrote: > You forgot about the ftp-masters, the release team and the security > team. They all have their word to say about which package can or cannot > be in the archive or part of a release. And usually they are not really > pro having the same code base twice in the archive.
The "right" way to achieve that would not be a separate source package upload, but for the original source package for a hypothetical program 'foo' to generate the existing 'foo' binary package and a 'foo-nosystemd' (or whatever) binary package as well. This is a geometric increase in packaging complexity and a maintainer (or team of maintainers) would likely only consider it if there was a very good reason for the new package, and sufficient resource in the team to manage the complexity of the packaging and the resulting extra bugs etc. -- Jonathan Dowland -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141026195417.ga...@chew.redmars.org
