From owner-freebsd-gnome@FreeBSD.ORG Wed Oct 6 00:51:51 2004 Return-Path: Delivered-To: freebsd-gnome@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4D5BC16A4D0; Wed, 6 Oct 2004 00:51:51 +0000 (GMT) Received: from creme-brulee.marcuscom.com (creme-brulee.marcuscom.com [24.172.16.118]) by mx1.FreeBSD.org (Postfix) with ESMTP id C925D43D46; Wed, 6 Oct 2004 00:51:50 +0000 (GMT) (envelope-from marcus@marcuscom.com) Received: from [192.168.1.4] (shumai.marcuscom.com [192.168.1.4]) i960pfQg010021; Tue, 5 Oct 2004 20:51:41 -0400 (EDT) (envelope-from marcus@marcuscom.com) From: Joe Marcus Clarke To: Jose M Rodriguez In-Reply-To: <200410051404.18385.freebsd@redesjm.local> References: <20041005015106.GG22274@toxic.magnesium.net> <1096942069.45818.5.camel@shumai.marcuscom.com> <200410051404.18385.freebsd@redesjm.local> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-B9pq8GukSZNDaSfo9fBf" Organization: MarcusCom, Inc. Message-Id: <1097023904.79913.24.camel@shumai.marcuscom.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Tue, 05 Oct 2004 20:51:44 -0400 X-Spam-Status: No, hits=-4.9 required=5.0 tests=BAYES_00 autolearn=ham version=2.64 X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on creme-brulee.marcuscom.com cc: FreeBSD GNOME Users cc: freebsd-gnome@freebsd.org Subject: Re: Gstreamer-plugins splitting ports .. needs testing and feed back ? X-BeenThere: freebsd-gnome@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: GNOME for FreeBSD -- porting and maintaining List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Oct 2004 00:51:51 -0000 --=-B9pq8GukSZNDaSfo9fBf Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Tue, 2004-10-05 at 08:04, Jose M Rodriguez wrote: > On Tuesday 05 October 2004 04:07, Joe Marcus Clarke wrote: > > On Mon, 2004-10-04 at 21:51, Adam Weinberger wrote: > > > >> (10.04.2004 @ 2143 PST): Michael Johnson said, in 2.0K: << > > > > > > > > - Figure out which ports use gstreamer-plugins and which > > > > plugins each needs > > > > > > > >> end of "Gstreamer-plugins splitting ports .. needs testing and > > > >> feed back ?" from Michael Johnson << > > > > > > I'd be interested in seeing the results of this sooner rather than > > > later; I still don't understand why this is necessary. For anything > > > that requires a libmad backend to gstreamer, we could just test for > > > something and make a ${BROKEN} error or something. > > > > That works when ports are being install interactively. However, when > > doing package building, we don't have that luxury. We could mark a > > port BROKEN if gstreamer-plugins was built without MAD support (the > > default), but that would mean we couldn't package it. > > >=20 > If gstreamer-plugins becomes a metaport selector, no port may depend on=20 > this. They must depends on a gstreamer-plugins-base and the plugins it=20 > really needs. >=20 > I think it must detect PACKAGE_BUILDING and only depends on=20 > gstreamer-plugins-base in that case. >=20 > 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 > > Splitting the port into multiple ports would give us the ability to > > package any port. An obvious example of this is the upcoming > > gnomemedia2 which will require CD Paranoia support in gst. > > > > The major disadvantage to this approach is the overwhelming > > administrative burden it adds. It's a pain to test [py-]libxml2 and > > [py-]libxslt. I can't imagine what a gstreamer-plugins update will > > do. For that reason, it might be nice to still have the ability to > > test-build all plug-ins in a monolithic way. > > >=20 > a gstreamer-plugins-test or gstreamer-plugins-devel port? Ideally, we shouldn't need an additional port. The gstreamer-plugins port should have the knobs to do this. However, if it would be easier, then creating a separate test port would be okay. Of course, if the maintainer(s) are willing to forgo this, and handle all the upgrade work themselves, who am I to complain. Joe >=20 > > Joe > > > > > # Adam > > > > > > > > > -- > > > Adam Weinberger > > > adamw@magnesium.net || adamw@FreeBSD.org > > > adamw@vectors.cx || adamw@gnome.org > > > http://www.vectors.cx > > > _______________________________________________ > > > freebsd-gnome@freebsd.org mailing list > > > http://lists.freebsd.org/mailman/listinfo/freebsd-gnome > > > To unsubscribe, send any mail to > > > "freebsd-gnome-unsubscribe@freebsd.org" >=20 > -- > josemi --=20 PGP Key : http://www.marcuscom.com/pgp.asc --=-B9pq8GukSZNDaSfo9fBf 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) iD8DBQBBY0Ggb2iPiv4Uz4cRAgkSAJ9xCLq4fQqgaNogLHoN1tFW3+fH8QCePWdP iF5PdsWf7V6SNpzQQnD919Y= =Q+Bl -----END PGP SIGNATURE----- --=-B9pq8GukSZNDaSfo9fBf--