Date: Mon, 28 Nov 2005 19:27:14 +0200 From: Ruslan Ermilov <ru@FreeBSD.org> To: John Baldwin <jhb@FreeBSD.org> Cc: cvs-src@FreeBSD.org, src-committers@FreeBSD.org, cvs-all@FreeBSD.org, "M. Warner Losh" <imp@bsdimp.com> Subject: Re: cvs commit: src/usr.sbin/config configvers.h mkmakefile.c src/sys/conf Makefile.alpha Makefile.amd64 Makefile.arm Makefile.i386 Makefile.ia64 Makefile.pc98 Makefile.powerpc Makefile.sparc64 files files.alpha files.amd64 files.i386 ... Message-ID: <20051128172714.GF62631@ip.net.ua> In-Reply-To: <200511281159.20751.jhb@freebsd.org> References: <200511272141.jARLfwca016783@repoman.freebsd.org> <200511280853.35658.jhb@freebsd.org> <20051128162447.GB62631@ip.net.ua> <200511281159.20751.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--FeAIMMcddNRN4P4/ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Nov 28, 2005 at 11:59:18AM -0500, John Baldwin wrote: > On Monday 28 November 2005 11:24 am, Ruslan Ermilov wrote: > > On Mon, Nov 28, 2005 at 08:53:32AM -0500, John Baldwin wrote: > > > On Sunday 27 November 2005 06:38 pm, M. Warner Losh wrote: > > > > How does this look to you? > > > > > > What is the point of the minor version number then if it is never > > > checked? I think we just should not do bumps for changes to config t= hat > > > allow old files to still work. IOW, the most recent bump should simp= ly > > > be reverted. In practice I don't think many folks other than develop= ers > > > ever end up with a config that is out of date with the kernel sources. > > > > The old config(8) against new files should also be considered. > > Otherwise, in this case, if it's reverted, how can I express > > that new sys/conf/files* require a new config(8)? The old > > config(8) will _appear_ to work with them, but will produce > > incorrect output (exactly the problem config version attempts > > to address). Specifically, "|" will be treated as a device. >=20 > Hmm, that change might actually warrant a bump then. Things like the=20 > 'machine' change would not warrant a bump however. >=20 Indeed, I didn't bump it for the "machine" change. The idea Warner attempts to implement is to bump a major whenever a backwards incompatible change is made, and bump a minor when a change is made such that a backward compatibility is not affected. This would allow for config versions >=3D the required version to work. I'd then bump the config version along with the change, and bump the required version in makefiles when doing a change to conf/files* (in this particular case). Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --FeAIMMcddNRN4P4/ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDiz3yqRfpzJluFF4RAjMCAKCdv1kyj47OpMaGp8yQfu8Lni8X7gCbBJ7u 1n97z5ZFM9TWdhrBKQR41AY= =D1pb -----END PGP SIGNATURE----- --FeAIMMcddNRN4P4/--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20051128172714.GF62631>