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