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. -- Hisham _______________________________________________ gobolinux-devel mailing list gobolinux-devel@lists.gobolinux.org http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
