> > > I first tried to use the un-official rpms to upgrade to kde2.2.1 but gave
> > > up after the cluster-f*** of lame dependency issues.
> > If you want a fully functioning system, you *do* need to install that
> > stuff.
> Wrong, if you want a non-functional system, then install that stuff.
Could you please explain this bizarre assertion?
> > > A dependency on mp3???
> > Well, Noatun will play MP3 files and it *does* need an MP3 decoder to do
> > so.
> > You can use some discretion here. If you aren't going to play MP3s you
> > don't need it. If you don't want to switch to CUPS, you don't need it.
> > ETC.
> A dependency on mp3?
Well, lets see, by "mp3" I presume that you mean: "libmp3lame.so.0".
What is your point? If you want to play MP3 files, then you DO need to
> > > I gave up soon after trying to get that working. Then I decided to try
> > > compiling it myself. Forget the intructions at kde.org, they're
> > > incomplete
> > These instructions assume that you have compiled something from source
> > before. If you need basic instructions on how to compile from source
> > you should look at a newbie site.
> Wrong again. I've compiled lots of stuff.
So what was the problem? I compiled it all from source. I had to
install some stuff (actually quite a bit of stuff) to have everything
functional, but I had no real problems.
As, I said, a list of what I needed would have helped, but that was the
> > > and if you ask 10 people what to do you get 10 different answers.
> > Actually, there is only one answer. You need to install all of the
> > needed support packages and if from binary (RPMs) then you also need the
> > corresponding 'devel' packages.
> There definitely is not only one answer. If there was we wouldn't be here.
People can tell you otherwise, but this is just BS.
Note to make this clearer, I said install 'all needed support packages'.
Some packages are optional (not 'needed') and you can decide if you want
to install them.
> > Then you can expect to have some problems that you will need to resolve
> > before the build is successful.
> > > I would bet that microsoft loves to see the linux community fractured and
> > > factionalized. Everyone has the best idea. Ours is better than theirs.
> > > Nana-nana-nana-nah. What bullshit. I would say the number one thing that
> > > should be worked out is to create some sort of dependency database online
> > > that could be used automatically to resolve dependency issues for the
> > > desktop/server user.
> > Your suggestions indicate that you do not understand the problem.
> I understand part of the problem. Factions.
Enlighten us! How do factions cause the need to upgrade and install a
lot of packages?
> > It is true that the README files that come with the source code is
> > outdated and inaccurate. It would certainly help if it included a list
> > of all packages that are needed to build the package.
> > But you do not understand the problem with binary RPMs. Many of the
> > dependencies for RPMs are not determined by the source that it was built
> > from, they are determined by the builder. So, there is no way that KDE
> > can tell you which packages you will need to install an RPM. Therefore,
> > the database you propose would not be possible. And, in any case, the
> > RPMs include a list of what they require, but you perceive this as a
> > problem. This list is the list of packages that it was built with and
> > you need them.
> I don't understand the problem completely but that doesn't mean it can't be
> solved. You really don't understand the issues if you think that it's just a
> simple matter of getting the right RPMS and then everything will be fine.
It always worked for me.
Quote:> You're either naive or your understanding of the problem is very incomplete.
OK, what don't I understand?
> Instead of the razzle-dazzle the kde (actually all linux programmers) should
> be making it stable. They should be working on the fundamentals of the
> software instead of adding new features.
That certainly is a valid point, but what does it have to do with the
> > There is also the UNIX syndrome which you may mistake for
> > factionalization. UNIX programs are usually dependent on a whole bunch
> > of stuff. You need to install this stuff -- that is just the way it is.
> Wrong again. If you think that the linux community is not factionalized
> then that shows you're entrenched and a part of the problem.
Your posting is an interesting rant, but what point can be make by
statements that are (or appear to be) contrary to fact without any
Perhaps you have a point. But, you have not clearly stated it. You
appear to think that the installation problems which you are having have
causes other than actual ones, and that installation can be simplified
ways which are impossible to implement.