Dear Martin,

I have an alternate proposal for handling this kind of BuildDepends issue:
a new field in fink that I'm tentatively calling InheritedBuildDepends.

Here's how it would work.  If package foo has the line
  InheritedBuildDepends: bar
then any time another package had a BuildDepends on foo, fink would 
automatically add a BuildDepends on bar as it was processing that other
package. 

(Or it could work another way: one could require that any time you are
building anything, and foo is present, then bar must be loaded before you
build.) 

This has the advantage of avoiding "Depends", which as we know is awkward
and can lead to problems when you want to remove certain -dev packages
automatically.  But, at least for cases like the gettext/libiconv problem,
it would lead to the desired result that *all* of the packages you need
are automatically present.

It would also be very useful in conjunction with pkgconfig.

I haven't thought about all of the examples you gave, to make sure that this
would solve them as well.

  Best,
  Dave


-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
_______________________________________________
Fink-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-devel

Reply via email to