| Summary: | layman doesn't look into make.conf for system variables | ||
|---|---|---|---|
| Product: | Portage Development | Reporter: | Alexey <lefsha> |
| Component: | Third-Party Tools | Assignee: | Gunnar Wrobel (RETIRED) <wrobel> |
| Status: | RESOLVED INVALID | ||
| Severity: | normal | CC: | n.oxyde |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Alexey
2006-10-15 06:16:53 UTC
(In reply to comment #0) > layman thinks that portage is always located in /usr/portage > which is wrong! > > instead layman should look into make.conf for that. > > please fix it. > This could be useful for PORTAGE_RSYNC_EXTRA_OPTS too. As far as I can tell the only place where layman uses the path "/usr/portage" is within the configuration file /etc/layman/layman.cfg. This can be changed :) I don't see where layman would use the path besides for the setting of the "storage" directory. @n_ox: I will mark this bug invalid because I believe the original report is nothing that needs fixing. If you feel layman should do something with the "PORTAGE_RSYNC_EXTRA_OPTS" setting, please open a new bug for that. At the moment there are no plans for layman to parse the /etc/make.conf file. |
