From owner-freebsd-ports@FreeBSD.ORG Sat Aug 11 10:00:35 2007 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D316816A500 for ; Sat, 11 Aug 2007 10:00:35 +0000 (UTC) (envelope-from freebsd.lists@fsck.ch) Received: from secure.socket.ch (secure.socket.ch [212.103.70.36]) by mx1.freebsd.org (Postfix) with ESMTP id 84DDA13C442 for ; Sat, 11 Aug 2007 10:00:35 +0000 (UTC) (envelope-from freebsd.lists@fsck.ch) Received: from 84-75-182-249.dclient.hispeed.ch ([84.75.182.249] helo=factory.fsck.ch) by secure.socket.ch with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67 (FreeBSD)) (envelope-from ) id 1IJnPP-000KIV-2P for freebsd-ports@freebsd.org; Sat, 11 Aug 2007 11:37:25 +0200 Message-ID: <46BD8352.4000605@fsck.ch> Date: Sat, 11 Aug 2007 11:37:22 +0200 From: Tobias Roth User-Agent: Thunderbird 2.0.0.6 (X11/20070804) MIME-Version: 1.0 CC: freebsd-ports@freebsd.org References: <20070811115642.L34115@obelix.home.rakhesh.com> <20070811084358.GA21364@rot26.obsecurity.org> In-Reply-To: <20070811084358.GA21364@rot26.obsecurity.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Spam-Score: 1.8 (+) X-Spam-Report: Spam detection software, running on the system "secure.socket.ch", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see The administrator of that system for details. Content preview: Kris Kennaway wrote: > On Sat, Aug 11, 2007 at 12:03:33PM +0400, Rakhesh Sasidharan wrote: >> Hi, >> >> Just a question that struck me today. Before there were the portupgrade >> and other tools for upgrading installed applications to their newer >> versions, how did things work out? >> >> Did one upgrade applications through a series of "make deinstall >> reinstall" commands (I wonder if these commands take care of dependencies >> too) or was there any other way? > > Basically that, plus a lot of other manual steps that were always > somewhat hard to get exactly right but which more or less worked back > in the days when Gnomes lived in your garden and Java was a place on > the map. It was a simpler, more innocent age. [...] Content analysis details: (1.8 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -1.4 ALL_TRUSTED Passed through trusted hosts only via SMTP 1.6 TVD_RCVD_IP TVD_RCVD_IP 0.0 DK_POLICY_SIGNSOME Domain Keys: policy says domain signs some mails 0.0 DKIM_POLICY_SIGNSOME Domain Keys Identified Mail: policy says domain signs some mails 1.6 MISSING_HEADERS Missing To: header X-SA-Exim-Connect-IP: 84.75.182.249 X-SA-Exim-Mail-From: freebsd.lists@fsck.ch X-SA-Exim-Scanned: No (on secure.socket.ch); SAEximRunCond expanded to false Subject: Re: How did upgrading applications happen before portupgrade etc? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Aug 2007 10:00:35 -0000 Kris Kennaway wrote: > On Sat, Aug 11, 2007 at 12:03:33PM +0400, Rakhesh Sasidharan wrote: >> Hi, >> >> Just a question that struck me today. Before there were the portupgrade >> and other tools for upgrading installed applications to their newer >> versions, how did things work out? >> >> Did one upgrade applications through a series of "make deinstall >> reinstall" commands (I wonder if these commands take care of dependencies >> too) or was there any other way? > > Basically that, plus a lot of other manual steps that were always > somewhat hard to get exactly right but which more or less worked back > in the days when Gnomes lived in your garden and Java was a place on > the map. It was a simpler, more innocent age. There was pkg_version -c that printed a sequence of cd /usr/ports/foo/bar make make deinstall make install make clean or something like that. Whatever broke was fixed manually afterwards :-) Oh, and there was no UPDATING in /usr/ports/ as well I think.