Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 06 Oct 2004 11:31:40 -0400
From:      Joe Marcus Clarke <marcus@marcuscom.com>
To:        Michael Johnson <ahze@ahze.net>
Cc:        freebsd-gnome@freebsd.org
Subject:   Re: Gstreamer-plugins splitting ports .. needs testing and feed back ?
Message-ID:  <1097076699.95993.8.camel@shumai.marcuscom.com>
In-Reply-To: <5AEB125E-1751-11D9-8817-000A958C81C6@ahze.net>
References:  <F0BECB69-166F-11D9-AC42-000A958C81C6@ahze.net> <20041005015106.GG22274@toxic.magnesium.net> <1096942069.45818.5.camel@shumai.marcuscom.com> <200410051404.18385.freebsd@redesjm.local> <1097023904.79913.24.camel@shumai.marcuscom.com> <5AEB125E-1751-11D9-8817-000A958C81C6@ahze.net>

next in thread | previous in thread | raw e-mail | index | archive | help

--=-EgPob/FRh/eqDumlNSSr
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Wed, 2004-10-06 at 00:36, Michael Johnson wrote:
> On Oct 5, 2004, at 8:51 PM, Joe Marcus Clarke wrote:
> >> On Tuesday 05 October 2004 04:07, Joe Marcus Clarke wrote:
> >>> On Mon, 2004-10-04 at 21:51, Adam Weinberger wrote:
> >>
> >> If gstreamer-plugins becomes a metaport selector, no port may depend=20
> >> on
> >> this.  They must depends on a gstreamer-plugins-base and the plugins=20
> >> it
> >> really needs.
> >>
> >> I think it must detect PACKAGE_BUILDING and only depends on
> >> gstreamer-plugins-base in that case.
> >>
> >> This is a real big 'logistic' effort.  It isn't by any means 'easy'.
> >
> > I don't really think we need a selector port, though that's certainly a
> > possibility.  These plug-ins are pretty useless by themselves.  They're
> > really only useful if another application will load them (yes, you can
> > use the GST command line tools, but how many users really do that?).
>=20
>=20
> Actually he may have a good idea, because there are ports like=20
> multimedia/gstreamer-player
> that will load and use any and every gstreamer plugin that it can find.
>=20
> we could add say USE_GSTREAMER=3Dall-select that will depend on=20
> gstreamer-plugins-select
> which will have a OPTION=3D for every plugin in bsd.gstreamer.mk
>=20
> But then again when package building what ports do we choose for=20
> defaults? Use USE_GSTREAMER=3Dall
> when PACKAGE_BUILDING is defined and depend on all 47 plugins?

I don't think that's necessary in this new scheme.  I think it's
sufficient to simply depend on the base set of plug-ins (i.e.
multimedia/gstreamer-plugins), then have users pick and choose the other
functionality they want.  Since each plug-in will now have its own
package, that's a breeze.  For example, for rhythmbox, I would have it
depend on the lame, mad, and ogg/vorbis plug-ins.  But for
nautilus-media, I would probably just depend on the base, and have users
add media support as they require it.

Joe

>=20
> Michael
--=20
PGP Key : http://www.marcuscom.com/pgp.asc

--=-EgPob/FRh/eqDumlNSSr
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (FreeBSD)

iD8DBQBBZA/bb2iPiv4Uz4cRAp0jAJsHGuhtGG4Qy+F4uvfs1fMmCzIjtACfYJRb
fBpEqBP+BVh6+mVI/sA9xMU=
=QX6u
-----END PGP SIGNATURE-----

--=-EgPob/FRh/eqDumlNSSr--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1097076699.95993.8.camel>