Subject: Re: CVS commit: pkgsrc/audio/gst-plugins-esound
To: Julio M. Merino Vidal <email@example.com>
From: Alistair Crooks <firstname.lastname@example.org>
Date: 06/21/2004 11:13:26
On Sun, Jun 20, 2004 at 08:44:48PM +0200, Julio M. Merino Vidal wrote:
> On Sun, 20 Jun 2004 20:30:50 +0000 (UTC)
> "Alistair G. Crooks" <email@example.com> wrote:
> > Module Name: pkgsrc
> > Committed By: agc
> > Date: Sun Jun 20 20:30:50 UTC 2004
> > Added Files:
> > pkgsrc/audio/gst-plugins-esound: buildlink3.mk
> > Log Message:
> > Add a buildlink 3 file for this package.
> May I ask why this file and the one in gst-plugins-mad are necessary?
> The stuff they provide don't need to be in the buildlink directories, so
> they seem useless from bl3's point of view. (jlam@ told me once that it
> was better to not use bl3.mk files where not needed).
> I've been using regular DEPENDS to use these gst-plugins-* packages from
> other ones, like gnome2-media or rhythmbox. They do, of course, include
> gst-plugins' buildlink3.mk file to get the libraries (which is what's
> needed in the buildlink directory).
I know my approach is different to yours, as I searched for
buildlink3.mk files for the other gstreamer plugins, and saw there
I used buildlink3 files because I would like one method in pkgsrc for
package pre-requisites, and buildlink3 fits the bill. I do think that
it is necessary in this case as well - the various gstreamer plugins
provide shared objects which are loaded at run-time, and I would like
to be sure that these shared objects are built with the correct paths
and run-time paths. I consider that buildlink is the best way to do