On 2011 m. rugpjūčio 7 d., sekmadienis 15:50:32 Joey Hess wrote: > Sven Joachim wrote: > > Hi folks, > > > > with this change from dpkg-dev git: > > > > ,---- > > > > | * dpkg-buildpackage no longer exports the compiler flags. Closes: > > | #560070 > > | > > | Packages must directly call dpkg-buildflags to retrieve them. > > > > `---- > > > > and the following from debhelper 8.9.4: > > > > ,---- > > > > | * dpkg-buildflags is only used to set environment in v9, to avoid > > | > > | re-breaking packages that were already broken a first time by > > | dpkg-buildpackage unconditionally setting the environment, and > > | worked around that by unsetting variables in the rules file. > > | (Example: numpy) > > > > `---- > > > > , compiler flags are not set at all for packages using dh-style rules > > files, unless those packages are upgraded to debhelper compatibility > > level 9. That does not seem to be an acceptable outcome. > > It's Not My Problem. Build flags are also not set for packages not using > dh.
I don't think it is a fair statement. Examples of minimal dh rules all over the place in your blog, debhelper package and dh manual page DO NOT have build flags handling. It is true that it's the result of inappropriate dpkg- buildpackage behaviour but it's still a bad practise pushed debhelper from the advent of dh so you should feel at least a bit responsible. I don't know the details what broke in the numpy package, but maybe a better solution could be found (dh-only?) for all compat levels... -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
