Summary: | make.conf(5) does not mention the source keyword | ||
---|---|---|---|
Product: | Portage Development | Reporter: | John Feuerstein <john> |
Component: | Documentation | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED FIXED | ||
Severity: | trivial | CC: | bernalex, binki, ormaaj |
Priority: | High | Keywords: | InVCS |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 472632 | ||
Attachments: | [PATCH] Fixes the bug |
Description
John Feuerstein
2010-03-17 13:37:56 UTC
We should also mention that variable substitution is supported. The description in make.conf(5) says only that the file contains "various variables". It's not obvious that make.conf isn't a shell script if a new user has only read the handbook. The manpage should say something along the lines of: "make.conf contains a newline-delimited list of <key>=<value> pairs which are accessible from the environment of ebuilds, /etc/portage/bashrc, etc, and supports a simple shell-like expansion of the form var="${var}", but doesn't support Bashisms like arrays or special parameter expansions." Also maybe direct them to the Python shlex docs for more details. It mentions for instance that comments can be processed by shlex.split() Created attachment 355718 [details, diff]
[PATCH] Fixes the bug
(In reply to Alexander Berntsen from comment #4) > Created attachment 355718 [details, diff] [details, diff] > [PATCH] Fixes the bug Thanks, this is in git: http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=ff54f5db6658c0bfecc7fe365d383c5879f20221 This is fixed in 2.2.0. |