Hi, On Thu, 25 Nov 2010, Roger Leigh wrote: > I don't see why we can't just mandate it in Policy, and then > enable it unconditionally if the Standards-Version is >= that > policy version. The package maintainer is declaring that their > package conforms to that policy version, which requires that > those targets be present. Easy and simple.
Jonathan made a nice summary and I'm following Russ's recommendation to not use Standards-Version for this. > This isn't an optional build feature like noopt, parallel etc. > It's something which we want to be the default. We shouldn't It's not clear at all that we want this to be the default. Only a tiny minority of packages benefit from the split build process. So it makes sense to use a capability label to enable it conditionnaly. > existing simple and robust mechanism to deal with this. This > has been an outstanding defect for over six years, and it's > incredibly frustrating that it's being held back by this > (unnecessary?) requirement. It's not been held back by this requirement. It's been held back by the lack of a nice and reliable way to auto-detect the available targets. And the lack of consensus on the best way to get forward. I have decided what I'm ready to accept and I will implement it at some point. But if you want to go faster, you're welcome to provide me a patch that I can accept... Cheers, -- Raphaël Hertzog ◈ Debian Developer Follow my Debian News ▶ http://RaphaelHertzog.com (English) ▶ http://RaphaelHertzog.fr (Français) -- To UNSUBSCRIBE, email to debian-dpkg-bugs-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
