Date: Thu, 01 Apr 1999 07:40:54 -0600 From: Jon Hamilton <hamilton@pobox.com> To: "Matthew D. Fuller" <fullermd@futuresouth.com> Cc: Satoshi - the Wraith - Asami <asami@FreeBSD.ORG>, jkh@zippy.cdrom.com, jhay@mikom.csir.co.za, current@FreeBSD.ORG Subject: Re: /var/db/pkg/.mkversion Message-ID: <19990401134054.7E7203E@woodstock.monkey.net> In-Reply-To: Your message of "Thu, 01 Apr 1999 05:28:39 CST." <19990401052839.D11572@futuresouth.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <19990401052839.D11572@futuresouth.com>, "Matthew D. Fuller" wrote: } [ Yes, I'm sticking my nose in where it probably doesn't belong and } should get chopped off for it. It's a hobby ;] } } On Thu, Apr 01, 1999 at 02:36:14AM -0800, a little birdie told me } that Satoshi - the Wraith - Asami remarked } > } > The same situation arises whether the version info is in /var/db/pkg } > or /some/other/place. It has been pointed out many times in the past } > that we need something to ensure bsd.port.mk can synchronize itself } > with the rest of the system (simply because there are too many people } > who cvsup one without the other). } > } > The question is, can I ask you to make sysinstall write some kind of } > version info that can be used by bsd.port.mk to identify the age of } > the system? } } This would require a little more work on the 'back' side, but what would } be so hard about just checking $Id$ strings around the .mk files? If } not for the revision, at least for the date. I think that's asking for trouble - it'll lose if someone keeps their .mk files in their own RCS (I do this for some files; admittedly not for the .mk files, but I could see someone doing that). -- Jon Hamilton hamilton@pobox.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990401134054.7E7203E>