Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 16 Apr 2012 00:46:00 +0300
From:      Ion-Mihai Tetcu <itetcu@FreeBSD.org>
To:        perryh@pluto.rain.com
Cc:        freebsd-ports@freebsd.org, annulen@yandex.ru, kob6558@gmail.com, nacho319@gmail.com
Subject:   Re: port variants
Message-ID:  <20120416004600.225bb4c6@it.buh.tecnik93.com>
In-Reply-To: <4f8966e2.OcinJeOK1WxrXm51%perryh@pluto.rain.com>
References:  <CAG_PEexDO2Shk_46RYpKyjpYakAGYp1mwPU7C=QUM7HbAdnNug@mail.gmail.com> <CAOjFWZ4womjueyvF4o6Yc_bQb2_DwoV5hMPJNx8EpqUaUCOFbw@mail.gmail.com> <0E61DE82-499B-47EF-9EEA-F9F3EB166A0A@gmail.com> <866281334347264@web24.yandex.ru> <CAN6yY1sEhiP51WDxAkYu7%2BbMknSeNWet7BmHNfHj2ML8ZzxtuQ@mail.gmail.com> <4f8966e2.OcinJeOK1WxrXm51%perryh@pluto.rain.com>

next in thread | previous in thread | raw e-mail | index | archive | help
--Sig_/K//c5RuTwPJRjeUVPgyloeB
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

On Sat, 14 Apr 2012 05:00:34 -0700
perryh@pluto.rain.com wrote:

> Kevin Oberman <kob6558@gmail.com> wrote:
>=20
> > While I think makefile-options is the way to go, I should also
> > point out that for the specific case of emacs and X11, it is
> > not used due to the very large differences. Other "variants"
> > are handled via options, but there are separate emacs and
> > emacs-nox11 ports.
> > ...
> > The port maintainer/developer has to make a call as to which
> > approach is more practical, but I suspect portmgr@ will press
> > for maximum use of makefile-options.

Unfortunately we can't force anyone to use OPTIONS. Yet.
I hope things will change once we get OPTIONS-NG in, since the new
framework will address (AFAIK) all the objections people have against
our current OPTIONS.

> One reason to use a slave port instead of an option is so that both
> configurations will be routinely build-tested, and corresponding
> packages made available.  Any one port can have only one "default"
> configuration.

Yes. We're lagging behind in this area.
With the new OPTIONS and the next iteration of pkgNG, this will be
hopefully solved. BUt it will take at least a year.


--=20
IOnut - Un^d^dregistered ;) FreeBSD "user"
  "Intellectual Property" is   nowhere near as valuable   as "Intellect"
FreeBSD committer -> itetcu@FreeBSD.org, PGP Key ID 057E9F8B493A297B

--Sig_/K//c5RuTwPJRjeUVPgyloeB
Content-Type: application/pgp-signature; name=signature.asc
Content-Disposition: attachment; filename=signature.asc

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (FreeBSD)

iEYEARECAAYFAk+LQZgACgkQJ7GIuiH/oeXC5ACdGG24TZpV8s6en6GqKPVW/EQL
MlUAn1WSMMcHeRBVTeh3BB5GoQH0D1+/
=pR+Q
-----END PGP SIGNATURE-----

--Sig_/K//c5RuTwPJRjeUVPgyloeB--



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