From owner-freebsd-arch Thu Jan 31 14: 8:12 2002 Delivered-To: freebsd-arch@freebsd.org Received: from ns.yogotech.com (ns.yogotech.com [206.127.123.66]) by hub.freebsd.org (Postfix) with ESMTP id EDED937B400 for ; Thu, 31 Jan 2002 14:08:03 -0800 (PST) Received: from caddis.yogotech.com (caddis.yogotech.com [206.127.123.130]) by ns.yogotech.com (8.9.3/8.9.3) with ESMTP id PAA29690; Thu, 31 Jan 2002 15:08:01 -0700 (MST) (envelope-from nate@yogotech.com) Received: (from nate@localhost) by caddis.yogotech.com (8.11.6/8.11.6) id g0VM7tj17305; Thu, 31 Jan 2002 15:07:55 -0700 (MST) (envelope-from nate) From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15449.49211.508201.314013@caddis.yogotech.com> Date: Thu, 31 Jan 2002 15:07:55 -0700 To: Garance A Drosihn Cc: nate@yogotech.com (Nate Williams), "Matthew D. Fuller" , arch@FreeBSD.ORG Subject: Re: Adding support for a global src tree serial number In-Reply-To: References: <3C5944A4.4927F812@mindspring.com> <80628.1012484102@axl.seasidesoftware.co.za> <15449.30438.698921.182380@caddis.yogotech.com> <20020131173702.J77899@genius.tao.org.uk> <20020131183321.GA59544@gattaca.yadt.co.uk> <20020131184230.D84715@genius.tao.org.uk> <20020131150720.A33201@over-yonder.net> <15449.45750.572076.480900@caddis.yogotech.com> X-Mailer: VM 6.96 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid Reply-To: nate@yogotech.com (Nate Williams) Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > > > > The problem is where to put the serial number, and how to > > > > distribute it. It needs to be maintained in a ,v file for cvs > > > > to be able to check it out. That adds additional complexity. > > > > > > Note also the additional trouble of underhandedly hand-crafting a > > > ,v-alike file will break checking out a revision other than the > > > absolute latest on the branch, since you'll end up with either no > > > serial, or still the latest serial, depending on how the file is > > > crafted. > > > >In general, that would only be a problem with folks that have the > >CVS tree who have updated their CVS tree but have not updated their > >/usr/src tree. > > Would it work for me? I have a local cvs tree which I update using > cvsup. It exists in a separate partition, /usr/cvs My proposal would work for you, since the 'file' would have at least one revision in it for every branch. > The machine is a dual-boot machine (-stable and -current). Both systems > mount the same /usr/cvs partition, and use it to update their respective > /usr/src's. How does each /usr/src get the correct serial-number, if the > serial-number file is not in cvs? That's my point. I think it *has* to be in CVS. > I agree that having the serial-number file in CVS is distasteful, due to > how often it will be changed, but it seems to me that is the only way to > have things work right for people who are using a local cvs > repository. We're in violent agreement here. :) Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message