On Sun, Sep 21, 2008 at 8:18 PM, Michael Homer > The solution to this "problem" is that you don't enable generic flags > you don't want to use, and you don't list programs you don't want to > use as part of the generics you *do* want to use. If you want to use a > specific implementation for a particular program, you enable that > implementation for that program. There is no case that isn't already > covered.
As long as everything defined under Data/DistUseFlags.conf (the purpose of which is not entirely clear to me) is overridable in Settings/UseFlags.conf, that sounds like a fair solution. My distant, high-level perception of the issue: if I don't have "tcltk" listed in my "gui" flags, or if I have "-tcltk" explicitly listed in my flags configuration, then I _really_ don't want to see any optional Tcl/Tk GUIs being built from any recipe I compile. OTOH, when I build aMSN, which has a Tcl/Tk GUI, I want that built on the basis that Tcl/Tk is a mandatory dependency for it, and therefore it should not be conditioned to a flag in the recipe. As long as these scenarios are maintained, I'm a happy camper. -- Hisham _______________________________________________ gobolinux-devel mailing list gobolinux-devel@lists.gobolinux.org http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
