From owner-freebsd-gnome@FreeBSD.ORG Thu Sep 9 20:41:29 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 5085A16A4D0; Thu, 9 Sep 2004 20:41:29 +0000 (GMT) Received: from toxic.magnesium.net (toxic.magnesium.net [207.154.84.15]) by mx1.FreeBSD.org (Postfix) with ESMTP id 07D2343D53; Thu, 9 Sep 2004 20:41:29 +0000 (GMT) (envelope-from adamw@magnesium.net) Received: by toxic.magnesium.net (Postfix, from userid 1252) id A8340DA889; Thu, 9 Sep 2004 13:41:28 -0700 (PDT) Date: Thu, 9 Sep 2004 16:41:28 -0400 From: Adam Weinberger To: Michael Johnson Message-ID: <20040909204128.GQ3649@toxic.magnesium.net> References: <947106C2-029D-11D9-B04C-000A958C81C6@ahze.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <947106C2-029D-11D9-B04C-000A958C81C6@ahze.net> X-Editor: Vim 6.2 http://www.vim.org X-Mailer: Mutt 1.5 http://www.mutt.org X-URL: http://www.vectors.cx X-ASL: 6/m/behind you User-Agent: Mutt/1.5.4i cc: FreeBSD GNOME Users cc: Mario Sergio Fujikawa Ferreira Subject: Re: multimedia/gstreamer-plugins request 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: Thu, 09 Sep 2004 20:41:29 -0000 >> (09.09.2004 @ 1619 PST): Michael Johnson said, in 1.7K: << > Hi, > > Gstreamer-plugins seems to keep getting bigger and bigger and more > and more > ports depend upon gstreamer-plugins. The problem with gstreamer-plugins > is that it > supports so much and is not built with many optional dependancies by > default. > A good example of a big problem is audio/rhythmbox, if you decide to > build it with > gstreamer-plugins and don't have mad and/or vorbis support in > gstreamer-plugins you have to rebuild > and reinstall gstreamer-plugins. Are there any other ports that require gst-plugins to be built with specific dependencies? None others come to mind. > My idea is splitting gstreamer-plugins in to smaller master/slave > ports, similar to what has happened > to all the php ports did last month. We have > USE_GNOME=gstreamer-plugins right now which works > but it is too broad and won't let you tell gstreamer "hey i need the > XXX plugin for this program to work!" > We need something that we can say we need XXX to run this. For exaple > USE_MULTIMEDIA=gstreamer-faad > would use the faad gstreamer plugin. I don't see how this would help. Gst-plugins isn't an incremental build. If you want to compile in new support, you need to rebuild the whole shebang. > In the long-term I think it would be smart to make USE_MULTIMEDIA (or > what ever we call it) support > more than just gstreamer-plugins because other multimedia ports such as > audio/speex have about > 15~ ports than depend on it so we could also do USE_MULTIMEDIA=speex, > this would save time and > effort in upgrading many ports. Or better yet, USE_MULTIMEDIA=xmms .... Honestly, I'd rather see energy put into reducing the number of macros that we have, not increasing it. The frameworks behind USE_GNOME and USE_SDL and the like are not trivial, and IMO shouldn't be implemented unless, as is the case for those two examples, there are literally hundreds of ports that will be greatly simplified by it. If you believe that your proposal would simplify things to such an extent, I'd like a bit more info about which ports would be simplified by it, and what its benefit would be to the end user. # Adam -- Adam Weinberger adamw@magnesium.net || adamw@FreeBSD.org adamw@vectors.cx || adamw@gnome.org http://www.vectors.cx