On 01/11/2011 12:59 AM, Nikos Chantziaras wrote:
On 01/10/2011 10:29 PM, Alex Schuster wrote:
[...]
The portage man page has some info about
this, it also mentions /etc/portage/package.env containing lines like
<category>/<package> <conffile>
with<file> being /etc/portage/env/<conffile>. It suggests to use this
instead of my approach I described above. I did not use this yet, I
assume it should be used when making generic changes for a package, but
as I want the change not for all GCCs, but only for certain slots, I use
the method I described.
Thanks for the pointer. It looks like this is even better since you only
need one file to deal with.
OK, just tried that. Works perfectly and without the "-g -g -g -g" glitch.
Thanks everyone for the responses :-)
