On Fri, 14 Dec 2012, Joey Hess wrote: > > But often dh-based packaging itself is simple/generic enough to work fine > > even > > with previous releases of debhelper still "in production" in Debian stable > > or > > its derivatives
> If a new compat level does not change a package, the package can be > left on the old compat level. but what if it does? but optionally, e.g. if I care to provide hardening build of cmake project for recent Debian releases but do not care to harden for previous release -- I need to have compat=9 so that recent debhelper appends CPPFLAGS to CFLAGS; and otherwise can drop compat down to 8 to build on older ones > The only problem with this is that it requires people to actually think > about whether a new compat level will affect a package, rather than > increasing to the new level because it's there and waiting to see if > something breaks. > But expecting packagers to select a range of compat levels that will > work is even more of a burden. So I don't see it helping. I am not asking to make it a requirement to specify the range, but a possibility ;) -- Yaroslav O. Halchenko Postdoctoral Fellow, Department of Psychological and Brain Sciences Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419 WWW: http://www.linkedin.com/in/yarik -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
