Summary: | app-portage/eix-0.10.2 /usr/bin/update-eix-layman assumes layman repository inside PORTDIR | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Lyall Pearce <Lyall> |
Component: | Tools | Assignee: | Stefan Schweizer (RETIRED) <genstef> |
Status: | RESOLVED FIXED | ||
Severity: | minor | CC: | martin, pacho |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Lyall Pearce
2008-01-29 10:11:31 UTC
(In reply to comment #0) > I believe it should use PORTDIR_OVERLAY (if defined in /etc/make.conf) No, this is not a good idea: PORTDIR_OVERLAY is not reserved for layman overlays. Typically, it is also used for local patches or ebuilds. In theory, update-eix-layman should have taken the value which the layman configuration defines for make_conf instead of ${LOCAL_PORTDIR}/local/layman/make.conf Unfortunately, parsing the layman configuration is not a trivial task and, moreover, would have to rely much on layman's internals (the same is true if python is used to let the layman libraries do the parsing). Having a separate configuration file for update-eix-layman is certainly overkill since most people have no use for it. Therefore, the intended solution for a situation like yours is that you use a wrapper or an alias which calls update-eix-layman -CA /portage/local/layman/make.conf instead of update-eix-layman. *** Bug 230788 has been marked as a duplicate of this bug. *** |