Re: BUILD_DEPENDS

[joerg%britannica.bec.de@localhost]

On Sun, Apr 30, 2006 at 07:48:11PM +0300, Aleksey Cheusov wrote:
> > On Sat, Apr 29, 2006 at 08:32:37PM +0300, Aleksey Cheusov wrote:
>  >> Can anybody explain me how I can use BUILD_DEPENDS?  Should I always
>  >> prefer pkgsrc variants of software or it is better to add new
>  >> requirements to BUILD_DEPENDS if a required programs/libraries/etc
>  >> is not in the base system (different BSDs, Solaris, Interix, ...)?
> 
> > What exactly do you want to depend on? The rules normally are:
> > (a) use USE_TOOLS if possible
> From documentation I didn't understand what kind of software
> can be mentioned in USE_TOOLS?
> autoconf, gmake? Fine.
> What about
> USE_TOOLS += I_am_the_only_person_who_knows_about_this_rarely_used_tool?
> I.e. how many tools (and what exactly) can be mentioned in USE_TOOLS?

The tools framework allows easy overriding of builtin tools, path names
etc. It is also handy to simplify *_DEPENDS. It doesn't apply for
anything. Reminds me that the list needs documenation.

> > (b) mark all tools, esp. msgfmt and friends as needed
> What do you think about this?
> .if ${OPSYS} != "NetBSD" # I know zlib is in NetBSD base system
> .include "../../devel/zlib/buildlink3.mk"
> .endif

Bad. devel/zlib/builtin.mk is responsible to decide whether to use the
native or pkgsrc version. Don't forget that pkgsrc is not only about
NetBSD and the set of system libraries varies greatly. Heck, the system
library might not be supported at all, e.g. NetBSD curses vs. ncurses.

> > (c) mark all dependencies on libraries, even if they might exist
> > natively. buildlink3 should take care of deciding that.
> PREFER_PKGSRC/PREFER_NATIVE?
> See above about libbz2.

That's what builtin.mk uses.

> > (d) avoid included versions esp. of "dangerous" libraries, prefer
> > external dependencies
> Do you mean = only, or >= and > too?
> What are "external dependencies"?
> audit-packages?

E.g. a bunch of packages ship versions of neon, libtiff, libpng, zlib
etc. Hack those to use the "external" versions from pkgsrc, if possible.
One important exception might be libjpeg, since it is sometimes needed
with different compile-time settings e.g. by ghostscript.

Joerg


-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
pkgsrc-wip-discuss mailing list
pkgsrc-wip-discuss%lists.sourceforge.net@localhost
https://lists.sourceforge.net/lists/listinfo/pkgsrc-wip-discuss