| 1 |
Bernd Steinhauser wrote: |
| 2 |
>> MPlayer has a psychological issue with 1.0 versioning, still 1.0.live |
| 3 |
>> correctly isn't higher than 1.0 |
| 4 |
> No, it is not. |
| 5 |
|
| 6 |
For mplayer it is correct. I'm MPlayer upstream as well. I do know. |
| 7 |
|
| 8 |
> In the -scm approach this means: |
| 9 |
> trunk = -scm |
| 10 |
> 4.1 branch = -4.1-scm |
| 11 |
|
| 12 |
so you'll be oblivious of changes needed inside the ebuild and you won't |
| 13 |
know what you merged last time you issued an emerge =foo-scm (that by |
| 14 |
itself it is a problem, since it is ambiguous) |
| 15 |
|
| 16 |
> With your approach, we would have to fix the version after every 4.1.x |
| 17 |
> release. That sounds awful, tbh. So: |
| 18 |
|
| 19 |
No that enforce people update the deps or at least gives one more reason |
| 20 |
to do. Keep in mind that -9999, -scm ebuild or .live templates aren't |
| 21 |
for public consumption. |
| 22 |
|
| 23 |
> trunk = .live |
| 24 |
|
| 25 |
nope it would resolve as foo_pre1 -> meaningless. |
| 26 |
|
| 27 |
> 4.1 branch = 4.1.1.live (before 4.1.1 has been released) |
| 28 |
|
| 29 |
correct, you can keep tracking 4.1.1, have interim snapshot pushed in |
| 30 |
portage to ~ if you are confident about them. |
| 31 |
|
| 32 |
> 4.1 branch = 4.1.2.live (before 4.1.2 has been released) |
| 33 |
> 4.1 branch = 4.1.3.live (before 4.1.3 has been released) |
| 34 |
|
| 35 |
same reasoning. |
| 36 |
|
| 37 |
lu |
| 38 |
|
| 39 |
-- |
| 40 |
|
| 41 |
Luca Barbato |
| 42 |
Gentoo Council Member |
| 43 |
Gentoo/linux Gentoo/PPC |
| 44 |
http://dev.gentoo.org/~lu_zero |
| 45 |
|
| 46 |
-- |
| 47 |
gentoo-dev@l.g.o mailing list |
Archives