| 1 |
sebasmagri@×××××.com wrote: |
| 2 |
> On Tue, Nov 25, 2008 at 03:18:11PM +0200, Nikos Chantziaras wrote: |
| 3 |
>> Nikos Chantziaras wrote: |
| 4 |
>>> I decided to give portage 2.1.6_rc1 a try. Now it wants to upgrade my |
| 5 |
>>> KDE3 to KDE4. I never unmasked or keyworded any KDE4 stuff. Any options |
| 6 |
>>> other than removing portage 2.1.6_rc1 again? |
| 7 |
>> On a similar note, what's the justification of having KDE4 in the same tree |
| 8 |
>> as KDE3? It's a different package altogether. It would have made more |
| 9 |
>> sense to have them in "kde4-base/*" etc. |
| 10 |
>> |
| 11 |
> Hi! |
| 12 |
> |
| 13 |
> kde3 and kde4 are slotted, so I don't think it's necessary to have |
| 14 |
> just-another-category for kde4... At last, kde4 is kde too... |
| 15 |
> in any case kde4 is willing to be installed without removing kde3... |
| 16 |
> |
| 17 |
> From my point of view it's impossible that portage upgrades kde3 to |
| 18 |
> kde4, if you really never unmasked or keyworded any kde stuff |
| 19 |
|
| 20 |
I didn't unmask nor keyword any *KDE4* stuff. Only KDE3. Previous |
| 21 |
portage was happy with that. The new portage is not. I have dozens of |
| 22 |
packages in package.keywords that look like this: |
| 23 |
|
| 24 |
kde-base/kdelibs |
| 25 |
|
| 26 |
Now portage wants to install the 4.1 versions of all those. The |
| 27 |
previous portage did not; I had to tell it to keyword the 4.1 versions |
| 28 |
if I wanted that. |
Archives