On Sun, Sep 29, 2013 at 04:48:08AM +0200, Guillem Jover wrote: > On Wed, 2013-09-25 at 22:52:08 +0200, Bill Allombert wrote: > > Package: dpkg-dev > > Version: 1.16.10 > > Severity: wishlist > > > To be reliable, dpkg-buildflags should provide a versionning system like > > debhelper does with debian/compat. > > > > dpkg-buildflags would defines a interface level (1,2,3,...) that is > > incremented > > each time the output of 'dpkg-buildflags --dump' change in the default > > configuration. Such interface level would be defined per vendor. > > > > Then dpkg-buildflags would provide an option --level <version> to choose the > > interface level to use. > > > > So 'dpkg-buildflags --level 1' would always return the same output even if > > dpkg-buildflags is updated to set different flags (unless the user override > > the default). > > > > This would allow to rebuild packages with newer dpkg-dev versions without > > the > > risk of getting different values for the flags that the original binaries > > used. > > Honestly I don't see the point in all this (at least not right now). One > of the reasons for dpkg-buildflags was to be able to do distribution-wide > global flags changes. If we have to modify each and every package in the > distribution to be able to make use of possible new flags that point is > defeated, we could as well switch back to manually setting them.
The idea is that using --level would not be mandatory. I think you are missing the big picture. Using dpkg-buildflags is not mandatory in any way, and to be useful for test archive rebuild, it needs to be widely supported. Using this system, packages maintainers can chose to use the current level or the latest level (whether they use --level or not), which is likely to increase support for dpkg-buildflags. Even if a package uses dpkg-buildflags --level, it is still possible to override the setting while doing a test archive rebuild, so it is better than not using dpkg-buildflags at all. > Also possibly adding this right now, would imply just churn for > maintainers, as the absence of level would need to be considered the > same as the first level introduced. No, the default would be the current behaviour which is to use the latest level. Cheers, -- Bill. <ballo...@debian.org> Imagine a large red swirl here. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
