From owner-freebsd-ports Mon Jun 23 22:39:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA24307 for ports-outgoing; Mon, 23 Jun 1997 22:39:32 -0700 (PDT) Received: from silvia.HIP.Berkeley.EDU (ala-ca11-15.ix.netcom.com [199.35.209.175]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA24301 for ; Mon, 23 Jun 1997 22:39:29 -0700 (PDT) Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.5/8.6.9) id WAA04606; Mon, 23 Jun 1997 22:39:23 -0700 (PDT) Date: Mon, 23 Jun 1997 22:39:23 -0700 (PDT) Message-Id: <199706240539.WAA04606@silvia.HIP.Berkeley.EDU> To: jfieber@indiana.edu CC: ports@freebsd.org In-reply-to: (message from John Fieber on Sat, 21 Jun 1997 09:43:32 -0500 (EST)) Subject: Re: Multiple versions of a ported item From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-ports@freebsd.org X-Loop: FreeBSD.org Precedence: bulk * Most ports that I'm aware of are of the type where you typically * have one version installed. If an upgrade comes along, you * either remove the old version and install the new, or just lay * the new on top of the old. Even where distinct versions of a * port exist, eg netscape3 and netscape4, you can really can only * have one installed at a time. For most ports that's true, but for tcl/tk and tiff, we have gone to great lengths to make some versions coexist (relatively) peacefully. Please try it.... * I'm sort of leaning toward the latter because the former could * generate a lot of ports and the space demands of including all * versions isn't very big. I see that you all imported it as one port contains all versions. I agree with that. Satoshi