| 1 |
Fernando J. Pereda wrote: |
| 2 |
> |
| 3 |
> On 14 Jun 2008, at 19:36, Luca Barbato wrote: |
| 4 |
> |
| 5 |
>> Bernd Steinhauser wrote: |
| 6 |
>>>>> With your approach, we would have to fix the version after every |
| 7 |
>>>>> 4.1.x release. That sounds awful, tbh. So: |
| 8 |
>>>> |
| 9 |
>>>> No that enforce people update the deps or at least gives one more |
| 10 |
>>>> reason to do. Keep in mind that -9999, -scm ebuild or .live |
| 11 |
>>>> templates aren't for public consumption. |
| 12 |
>>> Except, that it is not that easy. |
| 13 |
>>> The point of time where you have to update your kde deps has nothing |
| 14 |
>>> to do with that. |
| 15 |
>>> This is why we recommend to always reinstall everything from kde svn. |
| 16 |
>>> It is even more likely, that these problems occur after the "bump", |
| 17 |
>>> 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 |
> |
| 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 |
(btw they are single packages, emerge =python-9999 works as should) |
| 30 |
|
| 31 |
lu |
| 32 |
|
| 33 |
-- |
| 34 |
|
| 35 |
Luca Barbato |
| 36 |
Gentoo Council Member |
| 37 |
Gentoo/linux Gentoo/PPC |
| 38 |
http://dev.gentoo.org/~lu_zero |
| 39 |
|
| 40 |
-- |
| 41 |
gentoo-dev@l.g.o mailing list |
Archives