Bug 350381 – portage-2.1.9.25 does not allow capitals in filenames within /etc/portage/package.use/

• Product: Portage Development
• Status: RESOLVED INVALID

[Description David Flogeras 2011-01-02 16:09:35 UTC]

I wanted to add a filename in all caps in my /etc/portage/package.use dir so I would see it later to remind me to clean it up.  However, portage seems to not parse any files with capitals in their filename in said dir.  Oddly, it does not exhibit the same behaviour in the /etc/portage/package.keywords/ dir.

Using stable portage (2.1.9.25) on amd64

Reproducible: Always

[Comment 1 Zac Medico 2011-01-03 20:53:51 UTC]

It works for me, so I guess you must have some other cause at work here. 

The code is located in the grablines functions inside /usr/lib/portage/pym/portage/util/__init__.py. It only ignores files that start with "." or end with "~". The files are processed in alphabetical order.

[Comment 2 David Flogeras 2011-01-09 19:15:45 UTC]

Hmm, I put some print statements in the grablines function and can confirm it has parsed the file when it is named with all caps.

If I have a file /etc/portage/package.use/PORTAGE, containing just:
sys-apps/portage -doc

it parses it, but ignores the -doc:

Calculating dependencies... done!
[ebuild   R   ] sys-apps/portage-2.1.9.25  USE="doc (ipc) -build -epydoc -python3 (-selinux)" LINGUAS="-pl" 0 kB

Same results if the file is named /etc/portage/package/use/Portage

However, if I have a file /etc/portage/package.use/pORTAGE it works as expected (or /etc/portage/package.use/portage, etc.)...  Anything but starting with a capital letter I guess.

The sort function puts the file starting with capitals at the beginning of the list, but that shouldn't matter.  Anything else I can try/tell you?

[Comment 3 Zac Medico 2011-01-10 02:44:34 UTC]

My guess is that you have multiple settings for sys-apps/portage, and in this case the order of processing due to file names can make a difference. This might locate the settings:

  grep -r sys-apps/portage /etc/portage/package.use

If that doesn't find it, it may be to due to wildcard settings like these:

   sys-apps/*
   */portage

[Comment 4 David Flogeras 2011-01-10 10:56:57 UTC]

wow, I am an idiot.  funny thing is, both the original cause of my "bug", and the "sys-apps/portage -doc" (an example I just made up for the sake of this report because I thought I would pick a package I *definitely* hadn't modified myself) had other overrides.

embarrassing... sorry to waste the classroom's time!