Date: Fri, 26 Mar 1999 15:53:39 -0600 (CST) From: Steve Price <sprice@hiwaay.net> To: Satoshi Asami <asami@FreeBSD.ORG> Cc: sjr@home.net, jim@corp.au.triax.com, jorbeton@pilot.net, freebsd-ports@FreeBSD.ORG Subject: Re: CVSup and Fetch Message-ID: <Pine.OSF.4.02.9903261546550.22203-100000@fly.HiWAAY.net> In-Reply-To: <199903261348.FAA18790@silvia.hip.berkeley.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 26 Mar 1999, Satoshi Asami wrote: # How about something like this? A file (/var/db/pkg/VERSION) records # the "version" of the system. The "version" is a number derived by # concatenating the year/month/date -- so it's "19990326" today. If the # "version" is too old, bsd.port.mk refuses to do anything. # # bsd.port.mk has a variable that contains the required version. When I # know there is an incompatible update, I'll change the BSDPORTMKVERSION # line. # # There are a couple ways to update the version file. An upgrade kit # will of course fix it. Also, a "make world" will change it from # within src/share/mk/Makefile. This will be the date of the install, # not the date of the source, so it's actually possible that people can # still trip over by doing a new install on an old source tree...but the # alternative will be to encode something inside the source tree, which # I do not want to start doing again. # # Sample patch follows. You can see the change to 31upgrade/Makefile # too. 31upgrade/pkg/INSTALL just does a # # echo %%VERSION%% > /var/db/pkg/VERSION I like it! Though you might think about calling the file .version, .mkversion, .portmkversion, or something with a leading dot so it doesn't normally show up in an ls(1). -steve [pathes removed] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.OSF.4.02.9903261546550.22203-100000>