This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig4663B1910C057BA685C8CC15
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: quoted-printable

Freddie Cash wrote:

> All that's really needed is a more formalised process for handling
> upgrading config files, with as much as possible managed via the ports
> framework itself. Something that dictates the name of the config
> file, and that compares the config file from the port against the
> installed config file (or against an md5 of the port config file) and
> only replaces it if it is unchanged. Something that is part of the
> make system.


Most ports that install configuration files actually do this already.
It's generally why you'll find that a sample configuration file is
considered part of the port, but the actuall live configuration file
is not. The port will only feel free to meddle with the config file if
it is still identical to the sample file.

Cheers,

Matthew
--=20
Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard
Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
Kent, CT11 9PW


--------------enig4663B1910C057BA685C8CC15
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.8 (FreeBSD)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEAREIAAYFAkfmBpUACgkQ8Mjk52CukIz7gACeKksDBaAeA+ LOFirGFAtXNXGu
Va4An0edNTEQiIFNgXZmdloKSWrWegoe
=BBlJ
-----END PGP SIGNATURE-----

--------------enig4663B1910C057BA685C8CC15--