Philip Lamb wrote:
[]
> "When a package you are building has BuildDepends, you need to look into
> the .info file of each and every one of the packages that are depended
> upon, and add their BuildDepends to your BuildDepends line.
In addition to what Daniel said:
There are a couple of packages (two dozen or so in the gnome section)
that help you with this by including a list of inheritable
builddependencies. In their DescPackaging field, they say
Any package which BuildDepends on this one must also BuildDepend on:
This doesn't mean, of course, that packages which don't have this text
can never have similar requirements.
OTOH, watching the configure output for build dependencies is not a
purely mechanical task either. Lots of configure scripts needlessly test
for Fortran compilers, for example, and there may be many similar tests
for things that are never used in the package.
--
Martin
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Fink-devel mailing list
Fink-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fink-devel
