From owner-freebsd-ports Thu Mar 30 14:51: 8 2000 Delivered-To: freebsd-ports@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 3479A37BA48; Thu, 30 Mar 2000 14:51:05 -0800 (PST) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id OAA41798; Thu, 30 Mar 2000 14:51:04 -0800 (PST) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Thu, 30 Mar 2000 14:51:04 -0800 (PST) From: Kris Kennaway To: Satoshi - Ports Wraith - Asami Cc: ports@FreeBSD.org Subject: Re: final call: VERSION variable In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 30 Mar 2000, Satoshi - Ports Wraith - Asami wrote: > * Also a good idea, except it should probably be +VERSION for consistency > > No, I wrote it that way explicitly so users can install more than one > version of the same "port" if they want. Ultimately we want to go to > something like gnu stow (the /var/opt/pkgname/{bin,share,lib...} and > the symlink tree from /usr/local) and there is no reason why we have > to restrict ourselves to one version per port. The problem remains of how you actually locate this file to find out what version you have. Having a statically-named file with the version (or versions) in the contents is easy to read, having a dynamically named file means you have to scan the directory and parse the contents. Kris ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message