On Sun, 2005-07-24 at 15:19 -0500, Randy McMurchy wrote: > BLFS policy has always been to use whatever switches are necessary to > build *without* optional dependencies, with a note in the book explaining > what to do if they *are* installed. > > I am not trying to say what is right, or what is wrong. What you should > or should not do. I'm only stating what has been *BLFS' policy*.
Policy or not, there are cases like this one where packages should be considered strongly recommended even though not actually required. What percentage of people building a desktop are unlikely to want support for viewing the most common image formats? I suggest policy be amended to allow for cases where not including an optional dependency means losing functionality that the majority of people will use. By all means include instructions on how to build without the dependency, but use it by default. Simon.
signature.asc
Description: This is a digitally signed message part
-- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
