> On Sat, Apr 12, 2008 at 2:16 PM, Daniele Maccari <[EMAIL PROTECTED]> > wrote: >> >> Hisham wrote: >> > On Sat, Apr 12, 2008 at 11:01 AM, Daniele Maccari >> <[EMAIL PROTECTED]> wrote: >> > >> >> Jonatan Liljedahl wrote: >> >> > Or something like this: >> >> > >> >> > with_gtk1=( >> >> > "--enable-gtk" >> >> > "--disable-gtk" >> >> > ) >> >> > >> >> > or more self-documenting: >> >> > >> >> > useflag_gtk1=( >> >> > "with=--enable-gtk" >> >> > "without=--disable-gtk" >> >> > ) >> >> > >> >> > Those would be easy parsable by bash itself... >> >> > >> >> Sure, the possibilities are infinite :D >> >> >> > >> > True, but all the proposed variations just lighten the cumbersomeness >> > in a syntactic manner. The problem is not the size of each entry but >> > the number of entries and the implied maintenance issues. I find the >> > approach Michael described in his original post to be a good >> > compromise. And the $with_* variables scheme is especially smart! >> > >> > -- Hisham >> That's true too, so a question arises: is there some simple way to do >> this? > > To do what Jonatan asked for? I believe there isn't. The alternative > is to use ChrootCompile to make controlled builds of packages. > ChrootCompile should probably be enhanced with some knowledge about > how to handle these optional dependencies, but the biggest missing > block was to be able to tell recipes how to be behave on the presence > of these optional deps, and now we have that.
In what way is with_gtk1=("--enable-gtk" "--disable-gtk") not simple? I really think that <feature> should be *disabled* (not auto-configured) if that use_flag is specified as "without" (- instead of +) if it's possible. If I write "-gtk1" in my system wide useflag conf file, I expect all apps that *could* be built without gtk 1.x to not build with gtk 1.x. Without having to set up a chrooted build environment without gtk 1.x... >From a recipe perspective it's easy: if the option can be explicitly disabled, add a second element to the with_<feature> array. If not, leave it out or let it be an empty "" string. >From a script programming perspective it's also easy: if the flag was given as '+' use the first element of any with_<flag> variable, if the flag was '-' use the second element, if the flag was not specificed, do nothing. _______________________________________________ gobolinux-devel mailing list gobolinux-devel@lists.gobolinux.org http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel