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