"Thijs Kinkhorst" <[email protected]> writes: > Hardening-wrapper/includes have existed as the solution for build > hardening before dpkg buildflags was introduced. Therefore, quite a lot > of packages adopted hardening-wrapper/includes and put them into their > Build-Depends. Now that dpkg buildflags is the agreed-upon superior > solution, it is better if they move to this solution if possible. The > tag would alert them of this fact, as would it signal new packages > adding this method (e.g. by copying it from another package).
> There are still valid use cases, but as you say even there it's probably > a (known) bug in the build system that precludes the use of dpkg > buildflags. The packages themselves aren't going anywhere, it's just > that there's a large quantity of use that's most likely inertia. The > valid use cases could perhaps add an override? Hm, okay, yeah, that's a good point. -- Russ Allbery ([email protected]) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
