Luca Barbato schrieb:
> Bernd Steinhauser wrote:
>> In the -scm approach this means:
>> trunk = -scm
>> 4.1 branch = -4.1-scm
> 
> so you'll be oblivious of changes needed inside the ebuild and you won't 
> know what you merged last time you issued an emerge =foo-scm (that by 
> itself it is a problem, since it is ambiguous)
Huh? What has to do with the ordering?
And finding out what I installed last time is trivial and not the point.

>> With your approach, we would have to fix the version after every 4.1.x 
>> release. That sounds awful, tbh. So:
> 
> No that enforce people update the deps or at least gives one more reason 
> to do. Keep in mind that -9999, -scm ebuild or .live templates aren't 
> for public consumption.
Except, that it is not that easy.
The point of time where you have to update your kde deps has nothing to 
do with that.
This is why we recommend to always reinstall everything from kde svn.
It is even more likely, that these problems occur after the "bump", that 
shouldn't have been one at all.

> 
>> trunk = .live
> 
> nope it would resolve as foo_pre1 -> meaningless.
> 
>> 4.1 branch = 4.1.1.live (before 4.1.1 has been released)
> 
> correct, you can keep tracking 4.1.1, have interim snapshot pushed in 
> portage to ~ if you are confident about them.
Of course I can track 4.1.1 with -scm, too, but that was absolutely not 
the point and is by far not what I wanted.
The point was to track the 4.1 branch and not tags inside.


I have got a feeling, that you didn't have to deal with live packages 
that much yet. (No offense.)
-- 
gentoo-dev@g.o mailing list