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