| 1 |
Luca Barbato schrieb: |
| 2 |
> Bernd Steinhauser wrote: |
| 3 |
>> In the -scm approach this means: |
| 4 |
>> trunk = -scm |
| 5 |
>> 4.1 branch = -4.1-scm |
| 6 |
> |
| 7 |
> so you'll be oblivious of changes needed inside the ebuild and you won't |
| 8 |
> know what you merged last time you issued an emerge =foo-scm (that by |
| 9 |
> itself it is a problem, since it is ambiguous) |
| 10 |
Huh? What has to do with the ordering? |
| 11 |
And finding out what I installed last time is trivial and not the point. |
| 12 |
|
| 13 |
>> With your approach, we would have to fix the version after every 4.1.x |
| 14 |
>> release. That sounds awful, tbh. So: |
| 15 |
> |
| 16 |
> No that enforce people update the deps or at least gives one more reason |
| 17 |
> to do. Keep in mind that -9999, -scm ebuild or .live templates aren't |
| 18 |
> for public consumption. |
| 19 |
Except, that it is not that easy. |
| 20 |
The point of time where you have to update your kde deps has nothing to |
| 21 |
do with that. |
| 22 |
This is why we recommend to always reinstall everything from kde svn. |
| 23 |
It is even more likely, that these problems occur after the "bump", that |
| 24 |
shouldn't have been one at all. |
| 25 |
|
| 26 |
> |
| 27 |
>> trunk = .live |
| 28 |
> |
| 29 |
> nope it would resolve as foo_pre1 -> meaningless. |
| 30 |
> |
| 31 |
>> 4.1 branch = 4.1.1.live (before 4.1.1 has been released) |
| 32 |
> |
| 33 |
> correct, you can keep tracking 4.1.1, have interim snapshot pushed in |
| 34 |
> portage to ~ if you are confident about them. |
| 35 |
Of course I can track 4.1.1 with -scm, too, but that was absolutely not |
| 36 |
the point and is by far not what I wanted. |
| 37 |
The point was to track the 4.1 branch and not tags inside. |
| 38 |
|
| 39 |
|
| 40 |
I have got a feeling, that you didn't have to deal with live packages |
| 41 |
that much yet. (No offense.) |
| 42 |
-- |
| 43 |
gentoo-dev@l.g.o mailing list |
Archives