On 1/24/06, Bruce Dubbs <[EMAIL PROTECTED]> wrote: > Now what do we do? Change configure so it doesn't make an unnecessary > check for a package it doesn't need?
Report upstream. > That's a developer function, not > ours. Tell the user it is optional and let the warning shout that it > needs it? Yep. Lot of pacakges give out warnings. BTW, does it even link against libjpeg or is it just a configure check? > > According to kde, libjpeg is *recommended* for kdelibs, kdebase, > kdegraphics, kdemultimedia, and koffice. The easiest thing to do is to > just put it in aRts and keep configure quiet. It is recommended and > used in the next package (kdelibs) anyway. What if the user is just installing arts but not kde? > > The BLFS Book has the definition: "Recommended means that BLFS strongly > suggests this package is installed first for a clean and trouble-free > build, that won't have issues either during the build process, or at > run-time." That is the problem I have with the recommended. First it is the package maintainers that recommend a pacakge. On top of it we add our bloat^H^H^H^H^Hrecommendations:) -- 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
