Date: Tue, 8 Feb 2005 23:13:37 +0100 From: "Thomas E. Zander" <riggs@rrr.de> To: Pav Lucistnik <pav@freebsd.org> Cc: ports@freebsd.org Subject: Re: [Please test] mplayer-0.99.6 Message-ID: <20050208221337.GM68319@marvin.riggiland.au> In-Reply-To: <1107896833.67090.11.camel@hood.oook.cz> References: <20050207231916.GC68319@marvin.riggiland.au> <1107896833.67090.11.camel@hood.oook.cz>
next in thread | previous in thread | raw e-mail | index | archive | help
--zjcmjzIkjQU2rmur Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi, On Tue, 08. Feb 2005, at 22:07 +0100, Pav Lucistnik wrote according to [Re: [Please test] mplayer-0.99.6]: > [MPLAYER_CUSTOM_BUILD] > Why is this variable needed? >=20 > Users surely will want to just define WITHOUT_GUI=3Dyes and expect the > port to disable Gtk frontend, as it did up to now. This new variable > which have to be declared for WITHOUT_GUI to take effect looks like pure > annoyance to me. What's the background behind it? Well, annoyance is pretty hard imho. As I explained, there was some discussion going on in mplayer land, and most users (including myself) consider a good idea to be able to build some kind of 'official' binary package which includes some specific features and isn't built for a special CPU. In other words: It should be possible to build identical mplayer packages on different machines with different additional installed ports without tweaking make flags over and over. Until pre5, we automatically added dependencies and linked to the libs which are found on the system which results in a different mplayer port for almost any setup. To change this, I wanted to add a knob which defines dependencies on special features (and ONLY those features) to offer this possibility of unification. Now it's ok to discuss: Is it correct to set this binary-should-look- the-same-way-everywhere-build as the default as I did in the test port or should we think the other direction? I've chosen this course of action because I am of the opinion that build machines like our bento should be able to create the binary packages without having to define some knobs and without following a specific order of installing the ports in order to build a special package with the desired 'default' features. I thought it's not a big deal for users who install custom mplayers anyways just to define an additional make variable. Riggs --=20 - "[...] I talked to the computer at great length and -- explained my view of the Universe to it" said Marvin. --- And what happened?" pressed Ford. ---- "It committed suicide." said Marvin. --zjcmjzIkjQU2rmur Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- iD8DBQFCCTmRjdSJKchZls0RAlmDAJ96UyeMeCtrdtw8VmbOE9XMyT9bMgCfTZW7 AE439eBviKRvfiAwbLmmnjk= =OHuD -----END PGP SIGNATURE----- --zjcmjzIkjQU2rmur--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050208221337.GM68319>