Tiziano Müller wrote:
> Luca Barbato wrote:
> 
>> Tiziano Müller wrote:
>>> @lu_zero: I don't think we can get away without having the pm know what a
>>> live-ebuild exactly is and when to re-install it.
>> a live ebuild is a template, every time it has to be evaluated it acts
>> as a normal ebuild with the version mentioned and _preN+1 postponed,
>> preN is the highest preN present, if present.
> Sorry, but I don't want to re-install a snapshot every time I do a world
> update. And I also don't want to manually mask/unmask the live ebuilds.

This part of the behavior, when the update is triggered, isn't specified 
quite well, I'd trigger it when the cache gets invalidated, but I'm open 
to alternatives.

> I either want to be able to specify a time interval after which live ebuilds
> should be refetched or being able to manually re-install them (second use
> case is trivial).

Right.

> Ok, a solution to the problem for above (automatically re-install a live
> ebuild after a given time) would probably be to let the pm write a
> package.mask file which masks foo-1.2_pre${NUMBER+1} until the given time
> is elapsed and then change to mask to match foo-1.2_pre${NUMBER+2} to
> trigger re-installation (therefore "auto-masking/unmasking").

I see, that's ugly indeed.

lu

-- 

Luca Barbato
Gentoo Council Member
Gentoo/linux Gentoo/PPC
http://dev.gentoo.org/~lu_zero

-- 
gentoo-dev@g.o mailing list