From owner-freebsd-ports Fri Oct 8 20:16:11 1999 Delivered-To: freebsd-ports@freebsd.org Received: from mail.westbend.net (ns1.westbend.net [209.224.254.131]) by hub.freebsd.org (Postfix) with ESMTP id 04DF614FD4 for ; Fri, 8 Oct 1999 20:16:08 -0700 (PDT) (envelope-from hetzels@westbend.net) Received: from admin (admin.westbend.net [209.224.254.141]) by mail.westbend.net (8.9.3/8.9.3) with SMTP id WAA97571; Fri, 8 Oct 1999 22:17:31 -0500 (CDT) (envelope-from hetzels@westbend.net) Message-ID: <007801bf1204$9c607700$8dfee0d1@westbend.net> From: "Scot W. Hetzel" To: , "Mike Meyer" Cc: References: <199910082208.PAA74143@nimitz.ca.sandia.gov> Subject: Re: install newer version over old one... Date: Fri, 8 Oct 1999 22:15:59 -0500 Organization: West Bend Internet MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2014.211 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org From: Bruce A. Mah >Hmmm. I wrote that sentence poorly. What I meant is having the ability >to decide whether two ports referred to "the same" piece of software. >For example, ssh-1.2.27 and ssh-2.0.13 look (by the package naming >conventions) to be different installed versions of the same piece of >software. But they're actually very different. The ports directory >tries to differentiate these two (/usr/ports/security/ssh vs. /usr/ >ports/security/ssh2) but that distinction is lost in /var/db/pkg. > Then the ssh2 port needs to have it's package name changed to ssh2-2.0.13. >Consider also that both Tcl and Netscape Communicator both have >multiple ports in the ports tree. However, with Tcl (I think), you can >have multiple versions coexisting, but with Communicator, you can't. > This is where being able to set a variable (CONFLICTS) would allow you to specify which software can't have multiple software versions installed. >I was thinking that some kind of serial number might be useful to catch >small incremental changes (i.e. I added a patch but didn't change the >version number) but that sounds like a PITA and it's probably not the >right answer. The port would have to have a naming convention of: -[-] This is how NetBSD names their packages. When ever a Port Maintainer submits an update to a port they either increment the patch level (if the src version hasn't changed) or remove the patch level for a new src version. This is all accomplished with the patches that I had submitted to the PR Database: Port Conflict Checking - http://www.freebsd.org/cgi/query-pr.cgi?pr=13650 Patches to bsd.port.mk to check for version/port conflicts at install time. (requires pr bin/13649) Enhancement to PKG_INSTALL tools - http://www.freebsd.org/cgi/query-pr.cgi?pr=13649 Various enhancements to the PKG_INSTALL tools (pattern matching, conflict checking) Scot To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message