On Tue, 03 Apr 2012, Miguel Colon wrote: > Well any flag not only optimization levels are affected but -OX is > probably the most common case.
Any flag that allow overriding a previous value of the same flag and that maintainers are likely to change... wich doesn't make many. > Also some packages do > export DEB_CFLAGS_MAINT_SET=$(dpkg-buildflags --get CFLAGS) > which makes the -02 and the other flags permanent. This is a pretty stupid thing to do. What package is doing this? Is there a reason given? In any case, feel free to open a bug against the affected packages. > Anyway I just wanted to be able to be sure that the flags I wanted to > use for testing or building a local package for my system where > actually used without having to manually check each source to see if > there is a DEB_*_MAINT_* now or in the future that disables those > flags. I think the user should have the last say when building locally > since the user is willingly trying to use a flag locally but the > current method just adds the annoyance of either having to modify the > rules file, modify the BuildFlags.pm file or creating a gcc/g++ > wrapper. Well, I took the conservative approach in letting maintainers have the possibility to override/strip flags that are known to break the package. That way even if the user puts some dangerous flags in his default configuration, we maximize the set of packages that will continue to build. But obviously if you put yourself not as a user who needs the resulting package, but as a developer who is doing tests to see how many packages break with a given flag, then this decision might annoy you. We can invert the order between the maintainer environment variable and the user environment variable but I'd like the input of others because I can't really make up my mind on whether it's right and a realy useful thing to do. Cheers, -- Raphaël Hertzog ◈ Debian Developer Pre-order a copy of the Debian Administrator's Handbook and help liberate it: http://debian-handbook.info/liberation/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
