| Summary: | Possibility to make /etc/portage/make.conf a directory | ||
|---|---|---|---|
| Product: | Portage Development | Reporter: | Hanno Böck <hanno> |
| Component: | Core - Configuration | Assignee: | Portage team <dev-portage> |
| Status: | RESOLVED FIXED | ||
| Severity: | enhancement | CC: | nikoli, smkbot, tools-portage |
| Priority: | Normal | Keywords: | InVCS |
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Bug Depends on: | |||
| Bug Blocks: | 462382 | ||
Internally, we can implement this as a series of automatically generated 'source' commands, which will allow for precise reporting of file and line number for any syntax errors that may be encountered in the individual files. This is fixed in git: http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=86e75790954e766beba75443d967b2c25055c5b0 Enable recursion for make.defaults too: http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=90f0df42d8888d598e4a2f5cc891b2fcbef2f500 While I actually like this idea. Changing make.conf to a directory on a system will most likely break a lot of tools. The assumption for most tools is that make.conf is a bash sourceable file. Zac, Thinking out loud here, can we add a command to portageq that will return a list of make.conf files and the order they are processed by Portage? This will at least allow a tool to get the list and process them in the correct order. (In reply to comment #4) > Zac, Thinking out loud here, can we add a command to portageq that will > return a list of make.conf files and the order they are processed by > Portage? This will at least allow a tool to get the list and process them > in the correct order. Maybe it would be more useful to have portageq output all of the environment variables obtained from all sources including profile.env, make.globals, make.defaults, make.conf, and files sourced by make.conf? This is fixed in 2.1.11.59 and 2.2.0_alpha170. (In reply to comment #5) > Maybe it would be more useful to have portageq output all of the environment > variables obtained from all sources including profile.env, make.globals, > make.defaults, make.conf, and files sourced by make.conf? That would work. *** Bug 532664 has been marked as a duplicate of this bug. *** |
Currently it's possible to have multiple files of e.g. package.keywords and other portage-related configs by making a directory, e.g. /etc/portage/package.keywords/{a,b,c} However, this is not possible with make.conf. It would IMHO make sense for consistency of portage's behavior if it'd also be possible to have /etc/portage/make.conf/{a,b,c} (I'm aware that you can simulate similar behavior by using "source" in make.conf, so this is no severe issue, but nevertheless I think it'd be a feature that would make sense)