As part of implementing Variants, we have a need to specify conditional Depends (and BuildDepends, Conflicts, etc.). Maybe only some perl-versions need another package, or only the non -nox needs x11 stuff. I was thinking of a syntax something like these:
Depends: (string = /regex/) foo, (string ! /regex/) bar, biff, boff So if there is a parenthesized thing before a package, that package is disregarded if the preceeding expression is false (i.e., the regex does not match for =, or does match for !). For example: Depends: (%perlv = /56./) mime-base64-pm%perlv, compress-zlib-pm%perlv considering %perlv to be the XXX from the 'Type:perl X.X.X' (that expansion is just a hypothetical example at this point) would have the mime-base64 dependency for perl56X, but not for perl58X (since it is now part of perl58X-core) but compress-zlib would be a dependency for all perlXXX. And foo and foo-nox could both say: Depends: (%n = /-nox/) x11 I think this would only be for package-list fields (not *Script, etc.) since scripts can already use bash conditionals (and also it seems very much harder to figure out how to parse such a syntax for arbitrary script languages:) Thoughts? dan -- Daniel Macks [EMAIL PROTECTED] http://www.netspace.org/~dmacks ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
