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