>
> On Sunday 04 March 2001 15:58, you wrote:
> > --- civileme <[EMAIL PROTECTED]> wrote:
>
> > > There is no best way--you have 7.2 it depends what you put on it
> > >
> > > KDE 1.99 KDE 2.0 KDE 2.0.1 Any one of four sets from Chris Molnar?
> > >
> > > What I described wipes out what you had and allows a fresh install
> > >
> > > And if you don't want apmd, then rpm -ivh --nodeps kdeutils*rpm
> > > before installing the rest.
> > > Civileme
> >
> > Thanks for the advice. Thanks for the work with the kde packages too.
> > You guys got them done a lot sooner than I thought possible with Beta
> > and all. Not all agree with that but it's my opinion. Thanks.
> > I know how to install and agree that clean is best, too, & rpm
> > --rebuild does help to pack the base a bit after so much change.
> >
> > I simply wanted to know why there is a req in the pkgs to use APM. I
> > have not used APM for years. Now, I have to install it (to use
> > kdevelop) even though I am not going to use apmd. If I don't need it(
> > --nodeps), why is it there?
> >
> > Should I ask KDE or is this mdk req?
>
> ask KDE
>
> >
> > rj
> >
>
>
> Hmmm, KDevelop seems to be working on my machine and I did a --nodeps to
> avoid installing apmd, just on kdeutils. I also violated my own advice and
> left 2.0.1 Quanta and KOffice on and THEY work very well indeed. Of course,
> since you don't test, you might not be used to removing just those packages
> one intends to install. I wasn't sure it would work this way, but it did. I
> ripped out each kde package individually, with a --nodeps on removal where
> necessary, then installed KDE2.1 packages without any problem after the
> kdeutils and moving the package to a directory marked /done.
>
> Crashtesters report no additional bugs to the earlier reports here.
>
> The report of testing the kde packages is at
>
> http://perso.mandrakesoft.com/~civileme/kde_test_results
>
> That URL opens right to the text with Konqueror from 2.1.
>
> Civileme
>
> Additional reports are welcome, of course. I cannot possibly duplicate all
> the system setups out there.
>
>
> Civileme
>
>
It's not the --nodeps what is a problem(for me can't speak for rj) but the fact that
when i update kde in the future it will complain about it. Being on the cooker list
makes this naturally an highly unlikely.
