I have added a new file to the shared-libraries CVS module, called
BuildDepends.list .
If you are creating a new package and you want to be sure to cover all the
bases with BuildDepends, here's what you do:
1) Figure out everything that the package depends on (this includes
dependencies of dependencies, etc.). Note that a BuildDepends of
a Depends *doesn't* need to be included, but it shouldn't hurt to
include those as well.
2) For everything on your list, look it up in BuildDepends.list . If
"foo" is there, then there will be a reference to either "foo" or
"foo-dev". You add the appropriate one of those to your package's
BuildDepends list.
Sorry that it's not alphabetized! I might do that at some point. The syntax
is perl, so if you want, you can plug this into a perl script.
I'll try to keep this list up-to-date as the splitoff project continues.
-- Dave
_______________________________________________________________
Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
_______________________________________________
Fink-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-devel
