Several people have requested that 1) conditionals be implemented in
ConfigureParams (and perhaps the *Files and *Set* fields), and 2) a
way to apply a single conditional to more than one Depends
package. So...

1) It's easy to implement the same parenthesized conditional syntax on
CParams so that it applies to the next "word" (i.e., string of
non-whitespace and whitespace-in-quoted-string chars). That means
instead of having to do shell script with if/then/else to control
./configure flags, one could just say:
  ConfigureParams: (%type_pkg[-x11]) --with-x --mandir=%p/share/man

>From there, it doesn't seem like it would be hard to give the same
treatment to Files (and DocFiles). That way it would be easy for only
the -py21 variant to install a missing-feature-compatibility module or
packages where certain variants are "enhancements" that require
additional support/documentation/whatever files. Along with this,
fields that contain information about files (InfoDocs, Shlibs, etc.)
would disregard any entries for files that aren't actually in that
particular variant of the package. (This last is a pretty good sanity
check to implement regardless). Also, some package variants may need
slightly different CPPFLAGS (for example, setting configure options
for packages that don't use autconf).

2) Certain variants require more than one Depends (and related field)
addition. Currently, a conditional only applies to the single
following package. It's easy to implement this using a syntax of:
  BuildDepends: (%type_raw[-nox] != -nox) { gtk+, gtk+-dev }
And probably extensible to other conditionalizable fields.

Thoughts?

dan

-- 
Daniel Macks
[EMAIL PROTECTED]
http://www.netspace.org/~dmacks



-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g. 
Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
_______________________________________________
Fink-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-devel

Reply via email to