On Sun, Apr 15, 2012 at 01:49:33PM +0200, Ragnar Thomsen wrote: > > Well, for VLC, the configuration fails if these packages are not present or > the respective --disable-* switches not used. So if we set them as > recommended > deps, I guess we should have the disable switches in the instructions? Or > would it suffice to provide them in the command explanation section? > > I think it's difficult to draw the line. I guess the best strategy would be > to > list all deps that can be disabled with simple configuration switches as > recommended/optional. If more advanced deviations are needed, such as > modifying CFLAGS etc they should be required deps. > In general, if I list a package as recommended, I don't bother to explain how people can build without it. Some configure scripts will suggest that you perhaps meant to use --enable-fubar=no, others will make you dig through them to see if there is an option. No idea what the cmake equivalent behaviour is.
Similarly, I don't usually list how to enable optional packages. Soemtimes configure uses them automatically if they are found, other times a specific switch is needed. I agree with making pkgconfig recommended (where the package doesn't strictly require it : some refuse to configure if it isn't present) to avoid the insanity of pointing to the other required or optional packages. And, anything that needs glib2 now shows as requiring pkgconfig because of the changed dependency (pkgconfig used to use its own old glib). But yes, it's hard to draw the line, and things change over time. ĸen -- das eine Mal als Tragödie, das andere Mal als Farce -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
