Jonatan Liljedahl wrote: > Michael Homer wrote: > ... >> In most cases, dependencies are autodetected by configure correctly >> and no change to the Recipe file will be necessary. In that case, the >> with_<flag> variables should *not* be used only to convey redundant >> information, and the flag should just be listed appropriately in >> Dependencies. Note that this means that unlike Gentoo's, our flags are >> not exclusive: their support may be compiled in even if the flag is >> disabled, if the dependency is installed and autodetected correctly. >> Compilations using ChrootCompile will not experience this effect, as >> the dependency will be left out of the chroot environment. > > I don't like this, I might very well have some library installed just > because a few programs *need* it to compile, while I still want to avoid > using it in all apps that can manage without it. > > It may be libraries that I don't like, or that introduces > incompatibilities with other functions in the app (like karts or esd), > or that are deprecated and which I'm trying to get rid of (like GTK 1.x). > > This is easily fixed in the recipe: > > configure_options=( "--disable-gtk1" ) > with_gtk1="--enable-gtk1"
Another way would be to specify explicitly how to disable something: without_gtk1="--disable-gtk1" with_gtk1="--enable-gtk1" It may also sometimes be needed to have a not_using_<flag>() function, if the default is to include the behaviour of the flag and that exlusion can not be overridden by a using_flag() function like with overriding configure options... (BTW, I think the useflag for GTK 2.x should be called gtk2 and not just gtk. Some day there will be gtk3, etc... :) -- /Jonatan [ http://kymatica.com ] _______________________________________________ gobolinux-devel mailing list gobolinux-devel@lists.gobolinux.org http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
