Bug#1063605: debian-policy: mandate use of `dpkg-buildflags` for all software compilation on Debian
Bill Allombert <[email protected]>
| Newsgroups | gmane.linux.debian.devel.policy |
|---|---|
| Message-ID | <aYjavzMxQ6xRj0P7__7383.22567647032$1770576689$gmane$org@seventeen> |
On Sun, Feb 08, 2026 at 12:49:40PM +0000, Sean Whitton wrote: > Hello, > > > Packages that require special handling of compiler flags may selectively > > override the results of :command:`dpkg-buildflags` or avoid that command > > entirely, but only if the package maintainer is prepared to track future > > changes to the default compiler flags and update the package accordingly. > > This is normally only appropriate for packages such as ``glibc`` that have > > unique build considerations. > > LGTM, though as suggested by subsequent discussion, maybe you could > expand the last sentence's discussion to include reference to the other > sorts of packages that Bill and Simon raise -- especially the crypto > libs case. I would like to add that the flags set by dpkg-buildflags are not defined by the Debian policy. Cheers,