Re: about dpkg-buildflags
On Fri, Mar 19 2010, Raphael Hertzog wrote:
> Hi,
>
> let's have the discussion on the list please. Other people can have useful
> feedback on the design too.
>
> On Fri, 19 Mar 2010, Raphael Geissert wrote:
>> Yesterday I was writing a plan on how to implement what at the moment
>> I'm calling 'dpkg-buildflags' but was not sure how it was decided it
>> should pass the flags to debian/rules.
>>
>> I'm thinking about having a global (/etc/dpkg/buildflags{,.d}) config
>> and a local one (~/.dpkg-buildflags I guess). The script would take
>> those settings into consideration in addition to the env vars at the
>> time of its execution.
>
> There should be:
> - the default value provided by dpkg
> - which can be overriden/expanded system-wide with
> /etc/dpkg/buildflags (no .d, I don't think it's wise to let random
> packages modify the build flags for all packages built on the
> machine)
> - which can be overriden/expanded by the user with
> ~/.config/dpkg-buildflags (does it make sense to use XDG-compliant
> config filenames for the home directory?)
> - which can be overriden/expanded by the caller with envionment
> variables (DEB_CFLAGS_OVERRIDE / DEB_CFLAGS_APPEND ?)
>
> Must we support other operations besides replacing the value and
> appending more stuff to it?
Is there a way for the package maintainer to know what the
source of the value is? Somewhat like the origin function that Make
has?
manoj
--
Sigh. I like to think it's just the Linux people who want to be on the
"leading edge" so bad they walk right off the precipice. (Craig E. Groeschel)
Manoj Srivastava <srivasta@acm.org> <http://www.golden-gryphon.com/>
4096R/C5779A1C E37E 5EC5 2A01 DA25 AD20 05B6 CF48 9438 C577 9A1C
Reply to: