Note: Due to technical difficulties, the Archives are currently not up to date.
GMANE provides an alternative service for most mailing lists. c.f. bug 424647
>>>>> "ZM" == Zac Medico <zmedico@g.o> writes:
ZM> On 04/06/2010 07:22 AM, James Cloos wrote:
>>>>>>> "ZM" == Zac Medico <zmedico@g.o> writes:
>>
ZM> You can configure eclass override behavior via eclass-overrides in
ZM> /etc/portage/repos.conf, as documented in `man portage`.
>>
>> ,----< From that manpage >
>> | When using eclass-overrides, due to bug #276264, you must ensure that
>> | your portage tree does not contain a metadata/cache/ directory.
>> `----
>>
>> Which translates into "eclass-orderrides are completely and entirely
>> useless, so don't bother.
ZM> Well, it's roughly equivalent to the old default behavior (which you
ZM> apparently preferred). However, the issue is now complicated by the
ZM> fact that FEATURES=metadata-transfer is disabled by default, so when
ZM> portage goes to pull cache directly from metadata/cache/, it won't
ZM> be able to validate eclass changes since there are no eclass
ZM> timestamps saved inside metadata/cache/.
Portage does not need to validate eclass changes.
-JimC
--
James Cloos <cloos@...> OpenPGP: 1024D/ED7DAEA6
|
|
