On Mon, 23 Jun 2008, Felipe Sateler wrote: > > As such, it probably makes sense to add support for both in the same > > module but with different commands to allow checking one set or the other > > or both. > > I'm not really sure this is a good idea. The way I see it, Build-Options is > most useful for declaring that the package handles something that would break > a normal package (such as build-arch). Thus, I think they will be boolean (or > should, at least: I don't see the usefulness of parallel=n in Build-Options).
parellel=n was not the best example, but it could have been "maxparallel=n" for instance to indicate a limit on what it supports. Or maybe it could be "supported_flavors=gtk,kde,both" to explain us that we can use DEB_BUILD_OPTIONS="flavor=gtk" to build a gtk-only flavor of the package. In any case, I don't think it's wise to arbitrarily limit the use cases of those options and as such I'd prefer something that supports those richer semantics. Cheers, -- Raphaël Hertzog Le best-seller français mis à jour pour Debian Etch : http://www.ouaza.com/livre/admin-debian/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
