Summary: | --autounmask-write should write to a default file(name) in /etc/portage/package.*/ | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Jeroen Roovers (RETIRED) <jer> |
Component: | Core | Assignee: | Portage team <dev-portage> |
Status: | CONFIRMED --- | ||
Severity: | minor | CC: | doug, esigra, flow |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
See Also: | https://bugs.gentoo.org/show_bug.cgi?id=534548 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 376695 |
Description
Jeroen Roovers (RETIRED)
2012-02-22 16:23:39 UTC
It's not random. It's explained in the emerge man page since bug 370697: http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=424f8f8d6587f015e074e3e915746929a990a52f (In reply to comment #1) > It's not random. It's explained in the emerge man page since bug 370697: I'm sorry I used that word, but I did say "apparently random". > http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=424f8f8d6587f015e074e3e915746929a990a52f Couldn't emerge better make sure it's the last file by creating it? `zzzzz-autounmask' perhaps? Or even `ZZZZZ-autounmask'? (In reply to comment #2) > Couldn't emerge better make sure it's the last file by creating it? > > `zzzzz-autounmask' perhaps? Or even `ZZZZZ-autounmask'? I guess that could work. It has the disadvantage of forcing on the user a certain way of naming the files, though. You could add a file with a name that ensures that it is always the last one given your naming scheme and leave this file for portage. *** Bug 565564 has been marked as a duplicate of this bug. *** The current stage3 files ship with /etc/portage/package.use/iputils and autounmask likes to append changes to that file. New users might not immediately realize that all their changes are in the iputils file so can the empty zzzz-autounmask file be created as a default from now on? I've been creating /etc/portage/package.use/zzzz-autounmask for a long time now and it works very well. (In reply to Nathan Shearer from comment #6) > The current stage3 files ship with /etc/portage/package.use/iputils and > autounmask likes to append changes to that file. > > New users might not immediately realize that all their changes are in the > iputils file so can the empty zzzz-autounmask file be created as a default > from now on? > > I've been creating /etc/portage/package.use/zzzz-autounmask for a long time > now and it works very well. If we create it unconditionally, then it might interfere with whatever convention the user has chosen. For example, then might have numbered all of their files, and they've been using 9999-autounmask instead. Please see bug 598116 I also have working code in my SpecialFilename branch which has been tested. It could be modified to use a make.conf setting which a user could override the make.conf.defaults. https://github.com/dol-sen/portage-1/commit/c4a61bebca1cfeb0833cefb2c64be6156bdb8e8d Keep in mind, this code currently only kicks in if there are no files in the directory. |