Date: Wed, 2 Apr 2003 17:43:02 -0800 From: Kris Kennaway <kris@obsecurity.org> To: Andrew Sparrow <spadger@spadger.best.vwh.net> Cc: Kris Kennaway <kris@obsecurity.org> Subject: Re: Setting make options permanently (WITHOUT_GNOME, etc) Message-ID: <20030403014302.GC11467@rot13.obsecurity.org> In-Reply-To: <20030402221845.A66727@spadger.best.vwh.net> References: <5.2.0.9.0.20030402135505.00a10ec0@127.0.0.1> <20030402081419.54AB4E2@CRWdog.demon.co.uk> <20030402201530.GB9496@rot13.obsecurity.org> <20030402221845.A66727@spadger.best.vwh.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--7iMSBzlTiPOCCT2k
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Wed, Apr 02, 2003 at 10:18:45PM +0000, Andrew Sparrow wrote:
> On Wed, Apr 02, 2003 at 12:15:30PM -0800, Kris Kennaway wrote:
> > On Wed, Apr 02, 2003 at 12:14:19AM -0800, Andy Sparrow wrote:
> >=20
> > > For some bizarre and inexplicable (at least to me) reason, everyone w=
ho=20
> > > bikesheds around Yet Another Way to provide persistant build options =
to=20
> > > ports completely ignores this extremely convenient, pre-existing and=
=20
> > > perfectly functional mechanism.
> >=20
> > One of the design features of the ports collection is that it can be
> > used read-only, e.g. mounted read-only via NFS.
>=20
> I know thanks. I frequently update/install ports (and/or worlds,
> for that matter) on my firewall that were built on a faster machine.
>=20
> Other than the fact it's a little difficult for the port you're
> installing to create .install_done.${PORT} on a R/O FS, it seems to
> work fine.
That's what WRKDIRPREFIX is for. Of course, WRKDIR is not persistent
because it is deleted whenever you do 'make clean'.
> (and, IIRC, you may need to remove the .install_done file - from
> the serving machine, naturally - otherwise make thinks it doesn't
> need to do anything).
>=20
> > Makefile.local cannot be used there.
>=20
> I don't understand what you mean. The options in the file are used
> to build the port.
>=20
> If those options are not applicable to the machine on which you
> install it, then that's as doomed an act on the user's part as
> setting the CPU architecture to P4 on the building machine (e.g.
> in make.conf) and then installing the resulting binaries on a 486.
>=20
> Could you clarify your statement if I've misunderstood what you meant?
I meant that for people using a RO ports tree, Makefile.local in the
port directory is not an option. Given that this is a supported use
of the ports collection, Makefile.local cannot be a general-purpose
solution for storing local configuration state for the port.
> > > If I want to use BS dialogs[0] to configure things, I'll install Linu=
x=20
> > > or Slowaris, thanks very much. I *like* setting stuff once in text=20
> > > files, and I *like* unattended, automatic, recursive-with-my-local-op=
tion
> > > s ports upgrades[1] after my cvsup/build/installworlds.
> >=20
> > Don't use it then..easy!
>=20
> Some ports don't provide the ability to set build-time options
> either via the Make command-line, make.conf, pkgconfig or
> Makefile.local, they will instead implicitly start a dialog and
> prompt the user to interact with them, halting the build.
I was talking about my patches which replace the ad-hoc dialog
configurators in some ports. They allow you to choose not to enter
the configurator if you don't want to.
Kris
--7iMSBzlTiPOCCT2k
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (FreeBSD)
iD8DBQE+i5GmWry0BWjoQKURAgLbAJ4gwzNYBrS5Qcry0si5oxWVYwfV2QCePHF/
S2n2P0v6AF6rbtNfCmZpCFA=
=tzcy
-----END PGP SIGNATURE-----
--7iMSBzlTiPOCCT2k--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030403014302.GC11467>