BUILD_DEPENDS are only needed to build the package. If you want something
at runtime, use DEPENDS. Anyway, these are built *before* the package so
that they can also be used during the build time. And often, they are
needed. If they aren't... well, there is no solution. USE DEPENDS.

RUN_DEPENDS was removed some time ago. But I liked the SUGGESTS variable
Jan proposed...

HTH

On Tue, 24 Dec 2002 20:02:32 -0800
Frank Cusack <fcusack@fcusack.com> wrote:

> On Tue, Dec 24, 2002 at 07:34:37PM -0800, Jeremy C. Reed wrote:
> > On Tue, 24 Dec 2002, Frank Cusack wrote:
> > 
> > > I'm working on a local package which has
> > >
> > > DEPENDS+=	something-else
> > >
> > > That something-else is not a build-time dependency, and it takes VERY
> > > long to build.  Is there a way I can have make not build this dependency?
> > >
> > > It seems DEPENDS implies BUILD_DEPENDS.  How hard would it be to add a
> > > PACKAGE_DEPENDS or similar?  (I'd rather see DEPENDS implied meaning
> > > change, but that seems like too drastic of a change.)
> > 
> > Is it really a run-time dependency?
> > 
> > Tell us more. Because I don't understand why to use a DEPENDS if it is not
> > a dependency.
> 
> It is a dependency, but not at build time.
> 
> Consider gettext and gettext-lib.  gettext doesn't actually require
> gettext-lib to be installed, the reason it's there is to split out the
> libs so that some app can have only the -lib installed.
> 
> gettext has a RUNTIME depon gettext-lib, but not a buildtime dep.
> 
> /fc


-- 
Julio M. Merino Vidal <jmmv@menta.net>
The NetBSD Project - http://www.NetBSD.org/