--nextPart1798400.gxUiMzkLiq
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Tuesday 08 March 2005 07:52, Luke Mewburn wrote:
> On Tue, Mar 08, 2005 at 01:44:35PM +0100, Quentin Garnier wrote:
> I currently don't see the major benefit in providing different
> end-user configuration files based on MK<var> variable settings.

Not only that, but that way lies madness.

People who are tracking -current need to expect that once in a while the=20
bleeding edge will get sharper than other times and roll with it.

My major gripes are that building on one machine and rsync'ing the binaries=
=20
out is becoming a major pain recently.  I guess it's time to start some sor=
t=20
of cvs pool for my /etc config files, and some smart script to detect chang=
es=20
to /etc and to (perhaps) propagate them into other machine's configs=20
during /usr rsync.

pkgsrc is really making this harder every day, but I'm just told I'm doing=
=20
something odd and it would be easy if I just followed these simple steps=20
provided by lots of helpful yet not-doing-what-I'm-doing people.  (insert=20
about 20 annoyingly tedious steps here)

=2D-Michael

--nextPart1798400.gxUiMzkLiq
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (NetBSD)

iD8DBQBCLwyzl6Nz7kJWYWYRAgRlAJ9mk/adBtnJR2yDWJhMdBVfh39kvwCeJv2W
BHae6HEUumQIwEBTZESYUu4=
=+eAW
-----END PGP SIGNATURE-----

--nextPart1798400.gxUiMzkLiq--