| 1 |
On 14 Jun 2008, at 20:02, Luca Barbato wrote: |
| 2 |
> Fernando J. Pereda wrote: |
| 3 |
>> On 14 Jun 2008, at 19:36, Luca Barbato wrote: |
| 4 |
>>> Bernd Steinhauser wrote: |
| 5 |
>>>>>> With your approach, we would have to fix the version after |
| 6 |
>>>>>> every 4.1.x release. That sounds awful, tbh. So: |
| 7 |
>>>>> |
| 8 |
>>>>> No that enforce people update the deps or at least gives one |
| 9 |
>>>>> more reason to do. Keep in mind that -9999, -scm ebuild or .live |
| 10 |
>>>>> templates aren't for public consumption. |
| 11 |
>>>> Except, that it is not that easy. |
| 12 |
>>>> The point of time where you have to update your kde deps has |
| 13 |
>>>> nothing to do with that. |
| 14 |
>>>> This is why we recommend to always reinstall everything from kde |
| 15 |
>>>> svn. |
| 16 |
>>>> It is even more likely, that these problems occur after the |
| 17 |
>>>> "bump", that shouldn't have been one at all. |
| 18 |
>>> |
| 19 |
>>> emerge -C @kde-svn |
| 20 |
>>> |
| 21 |
>>> emerge @kde-svn |
| 22 |
>>> |
| 23 |
>>> that should suffice. |
| 24 |
>> I don't see that working for something like, say, python or glibc. |
| 25 |
> |
| 26 |
> do you really want to use live ebuild of THOSE? |
| 27 |
|
| 28 |
Why not? |
| 29 |
|
| 30 |
> (btw they are single packages, emerge =python-9999 works as should) |
| 31 |
|
| 32 |
So what was your proposal all about? |
| 33 |
|
| 34 |
- ferdy |
| 35 |
|
| 36 |
-- |
| 37 |
gentoo-dev@l.g.o mailing list |
Archives