see URL Reproducible: Always Steps to Reproduce: 1.euses boundschecking 2. 3.
URL corrected example from make.conf: CFLAGS= "-O2 -pipe march=core2"
Please post/attach all relevant information right here.
euses correctly assumes shell compatibility of make.conf, only it isn't documented anywhere and sys-apps/portage doesn't mind. So we should document this restriction.
The getconfig() function already has a warning about \r characters. We should add warnings for other shell incompatibilities as well.
Created attachment 248544 [details] output of euses
Created attachment 248546 [details] my make.conf
Created attachment 248547 [details] emerge --info
Um, couldn't you please alter euses the way that it just filters space and tab? I remember that at least one other portage tool was altered that way too...
(see bug #105069 please)
(In reply to comment #8) > Um, couldn't you please alter euses the way that it just filters space and tab? > I remember that at least one other portage tool was altered that way too... Well, now that this is assigned to dev-portage you'll also probably want to convince us not to produce warnings about this syntax? What's wrong with requiring shell-compatible syntax?
(In reply to comment #8) > Um, couldn't you please alter euses the way that it just filters space and tab? > I remember that at least one other portage tool was altered that way too... The standard has always been that make.conf is shell compatible, only we never put that in writing. If you want to change this de facto standard, then you will need to bring this up on the gentoo-dev mailing list and get some kind of majority to support the change. And you will have to propose a proper new standard too, not just request that spaces in variable assignments are to be allowed.
Well, the only reason I can tell now is that the suggested behaviour would be more user friendly. If bringing the topic to the mailing list is an option I'll think about that. For the time being an alias euses='PORTDIR=/var/portage euses' put into the .bashrc works (same for eix-update - but that's another story). As well I set the severity to 'enhancement' if that's ok for you.
Version no longer in Portage.
Zac, any ideas on how to solve this simply (implementation-wise)? If you have any pointers/advice I can work on it later.
(In reply to Alexander Berntsen (RETIRED) from comment #14) > Zac, any ideas on how to solve this simply (implementation-wise)? If you > have any pointers/advice I can work on it later. Maybe this library will help: https://github.com/sloria/environs We can use it when available, and otherwise fallback to our existing portage.util.getconfig() implementation.