On Wednesday 19 December 2001 18:26, you wrote:
> On Wed, Dec 19, 2001 at 05:57:51PM +0100, RA wrote:
> > On Wednesday 19 December 2001 17:31, you wrote:
> > > >I've got now a ~ 1 month old cooker installation. Now I decided to
> > > > update some kde-2.2.2 packages via urpmi, basically 'urpmi kdelibs'
> > > > or 'urpmi kdelibs-2.2.2'.
> > > >But urpmi chooses also libqt3, kdelibs-3.0beta, libarts3 among other
> > > > 2.2.2 packages.
> > > >So maybe you have to unscramble some dependencies.
> > >
> > > Maybe you have to remove the contrib source from your urpmi setup...
> >
> > Yes, that would be a possibility. But nevertheless I don't understand why
> > libqt3 and kde3 were chosen as upgrade.
>
> It's because:
>
> a) there's no such thing as "main","contrib","whatever" for urpmX
> all packet sources are alike
> b) naturally foobar-3.0 is a successor of foobar-2.2 - so
> kdelibs-3.0beta would be naturally an up{date|grade} to kdelibs-2.2
>
> Why are those packages named this way after all? What about versioning?
> what about:
> kdebase3.0-3.0.0-0.1mdk
> kdebase-devel3.0-3.0.0-0.1mdk
> ...
>
> just like in gcc/gcc3.0 ... then such things would not happen.
>
> On the other hand, it might not be useful to versionate KDE as it makes
> no sense to install two or more versions along - alas "update-alternatives"
> is used propperly ..
>
>
> Christian
Oh, yes. Pretty clear if one drinks no gluehwein...
