From owner-freebsd-ports Mon Mar 11 21:55:53 1996 Return-Path: owner-ports Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id VAA01832 for ports-outgoing; Mon, 11 Mar 1996 21:55:53 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id VAA01825 Mon, 11 Mar 1996 21:55:51 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.7.4/8.6.9) with SMTP id VAA00645; Mon, 11 Mar 1996 21:54:23 -0800 (PST) To: Garth Kidd cc: asami@cs.berkeley.edu (Satoshi Asami), torstenb@freebsd.org, ports@freebsd.org Subject: Re: ssh port update In-reply-to: Your message of "Tue, 12 Mar 1996 10:17:50 +0930." <960312141835.ZM2871@jolt.systems.sa.gov.au> Date: Mon, 11 Mar 1996 21:54:23 -0800 Message-ID: <643.826610063@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-ports@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I'll try the official port. One question; should I use pkg_manage to > delete my original attempt first? Will it get confused if I just go ahead > and make install again? I would just make install again. Also, don't get too comfortable with pkg_manage - it's gone away in -current and will eventually (soon I hope) be replaced with something better. > [Related: I'm about to upgrade from fvwm 1.x to fvwm 2.x; should I delete > the old one first with pkg_manage?] I most definitely would not do that - I played with fvwm2 a bit (which co-exists perfectly happy with the first version of fvwm - the port maintainer being quite careful about this, I was very happy to see) and I didn't like it at all. I quickly ran back to the original. Jordan