>> 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.
>

True, I was also thinking about the "silly" case when someone used
DEB_*_MAINT_SET which I would guess break noopt and disable any user
flag.

>> 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.
>

Oh I was trying to search how many packages currently use
DEB_*_MAINT_* options and found that one with a web search. I did not
try an exhaustive search (should not be that many anyway) since it was
5am and this is more of a wishlist type of change since from the
original email I gathered that this behavior was intentional by dpkg.

The package that did this was http://packages.debian.org/sid/crash
from what I remember.

I will open the bug when I get home in a couple of hours if there is none.


> 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.
>

True, I noticed this testing some packages with gcc-4.7 and custom
flags with a custom pbuilder script. I was trying to remove the ugly
gcc-wrapper that I used to insert/remove flags and try a cleaner
approach and then found this.

> 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.
>

This sounds reasonable, thanks!.

Cheers,
Miguel



-- 
To UNSUBSCRIBE, email to debian-dpkg-bugs-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to