On 1/23/06, Randy McMurchy <[EMAIL PROTECTED]> wrote: > > What you mention here is a *mistake* by an editor. And that editor > was probably me. I cannot find where jpeg is mentioned as a recommended > dependency by the KDE devs in any of the docs. Though it is recommended > by almost every other package, aRts is not one of them. I probably > goofed on this one.
My intention was not to point it out as a mistake coz I don't know it was a mistake. My point is when there is a recommended section, the interpretation is subjective. So what is a *must want* dependency for one person may turn out to be useless for someone else. Personally I try to build each pacakge with as little dependency as possible and add optional dependencies as per my needs. This allows me to reduce the dependencies in the pacakges I install. So when I upgrade (I prefer upgrading rather than rebuilding my entire installation) I have few package breakages to worry about. > > Why is it that you guys won't write in about these observations > earlier? Surely, you just didn't go through the book tonight because > of this thread looking for instances. It would be nice if things > like this were mentioned when they are discovered. I went thru the book y'day to make a list of pacakges that I need to install. Noticed that but since I have not yet compiled arts, I was not sure why the dependency was required. Will of course point out things that I notice as I compile them. -- Tushar Teredesai mailto:[EMAIL PROTECTED] http://www.linuxfromscratch.org/~tushar/ -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
