Re: [gentoo-portage-dev] support multiple eclass variants (aka "unstable eclasses")

[Sebastian Luther]

Am 14.07.2014 12:49, schrieb Michael Haubenwallner:
> 
> Is there an easy way to use the eclasses from the overriding tree, but not 
> the (usually newer)
> ebuilds from there - such as 'configure but disable repo (except for use in 
> eclass-override)'?
> 

Putting */*::repo_name into p.mask should remove all effects. Let me
know if there's another effect you want to disable. You may need
--autounmask-keep-masks to prevent emerge from unmasking those ebuilds.

> Thanks!
> /haubi/
> 
> 

Re: [gentoo-portage-dev] support multiple eclass variants (aka "unstable eclasses")

[Michael Haubenwallner]

On 07/08/2014 07:11 PM, Sebastian Luther wrote:
> Am 08.07.2014 18:58, schrieb Michael Haubenwallner:
>> Hello fellow Portage developers,
>>
>> attached portage patch draft aims to allow for easy distributing eclasses to 
>> be tested by
>> multiple tinderboxes on various architectures, without being active for 
>> normal installs.
> 
> What does the patch allow you to do, that you can't do right now? (i.e.
> put an eclass with the same name in an repository and use
> eclass-overrides to force its use in another repo?)

Is there an easy way to use the eclasses from the overriding tree, but not the 
(usually newer)
ebuilds from there - such as 'configure but disable repo (except for use in 
eclass-override)'?

Thanks!
/haubi/