> I'm not sure what the proper approach would be. On the other hand, I'm not > entirely convinced that it's important to let the user have the last word > in cases where maintainers have opted for a specific optimization level: > - building with -Os is typically made for udeb and I don't see a > compelling reason to have the possibility to change the maintainer > choice via the environment variable > - building with -O3 is often picked as a work-around when -O2 doesn't give > the expected result, why would you want to pick another optimization > level? if you want -O0, then it's the noopt option that you should be > using
Well any flag not only optimization levels are affected but -OX is probably the most common case. Also some packages do export DEB_CFLAGS_MAINT_SET=$(dpkg-buildflags --get CFLAGS) which makes the -02 and the other flags permanent. 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. -Miguel -- To UNSUBSCRIBE, email to debian-dpkg-bugs-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
