Bernd Steinhauser wrote:
MPlayer has a psychological issue with 1.0 versioning, still 1.0.live
correctly isn't higher than 1.0
No, it is not.
For mplayer it is correct. I'm MPlayer upstream as well. I do know.
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)
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.
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.
4.1 branch = 4.1.2.live (before 4.1.2 has been released)
4.1 branch = 4.1.3.live (before 4.1.3 has been released)
same reasoning.
lu
--
Luca Barbato
Gentoo Council Member
Gentoo/linux Gentoo/PPC
http://dev.gentoo.org/~lu_zero
--
gentoo-dev@lists.gentoo.org mailing list
