I don't actually see anything in current policy that mandates the
reading that configuration files are "any file that someone may wish to
edit". This is generally good sense, but there may be other factors
(such as the cost of debugging a transition path for the file, and the
impending freeze); so I don't really think this is release-critical, and
I also don't think it's a policy violation, strictly speaking.
--=20
Steve Langasek
postmodern programmer
--76DTJ5CE0DCVQemd
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline
Message-ID: <email address hidden>
Date: Wed, 30 Mar 2005 19:38:04 -0800
From: Steve Langasek <email address hidden>
To: <email address hidden>, Manoj Srivastava <email address hidden>
Subject: Re: Configuration file not under /etc
--76DTJ5CE0DCVQemd Disposition: inline Transfer- Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
Content-
Content-
severity 236252 important
thanks
Hi Manoj,
I don't actually see anything in current policy that mandates the
reading that configuration files are "any file that someone may wish to
edit". This is generally good sense, but there may be other factors
(such as the cost of debugging a transition path for the file, and the
impending freeze); so I don't really think this is release-critical, and
I also don't think it's a policy violation, strictly speaking.
--=20
Steve Langasek
postmodern programmer
--76DTJ5CE0DCVQemd pgp-signature; name="signature .asc" Description: Digital signature Disposition: inline
Content-Type: application/
Content-
Content-
-----BEGIN PGP SIGNATURE-----
ufymYLloRAkvYAJ 0cMoTqWoyScyv+ fApuAssjccdUtwC gjSJf YVIgRXJ0=
Version: GnuPG v1.4.0 (GNU/Linux)
iD8DBQFCS3CXKN6
AHgpYXjp4IrUiLT
=Yydy
-----END PGP SIGNATURE-----
--76DTJ5CE0DCVQ emd--