On Fri, 24 May 2002, Johnny Lam wrote:

> > Thanks for replying. I looked around and I ended up using:
> >
> > .include "../../audio/libaudiofile/buildlink.mk"
> > .include "../../devel/glib/buildlink.mk"
> > .include "../../x11/gnome-libs/buildlink.mk"
> > .include "../../mk/x11.buildlink.mk"
> > .include "../../mk/bsd.pkg.mk"
> >
> > (I am not sure why it has libaudiofile and esound, since not needed for a
> > unzipping.)
>
> gnome-libs depends on esound which depends on libaudiofile.  You can
> compact the above into just:
>
> .include "../../x11/gnome-libs/buildlink.mk"
> .include "../../mk/x11.buildlink.mk"
> .include "../../mk/bsd.pkg.mk"

I believe what he's asking is "Why?", since not everything that needs
gnome-libs really needs the audio support. So while including
buildlink.mk's in other buildlink.mk's saves typing for pkgsrc
developers, it results in erroneous dependencies in the binary packages.

Frederick