Date: Fri, 22 Oct 2004 01:30:28 GMT From: Justin Hawkins <justin@hawkins.id.au> To: freebsd-ports-bugs@FreeBSD.org Subject: Re: ports/72547: [PATCH] www/twiki: update to 20040901 Message-ID: <200410220130.i9M1USBM028914@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR ports/72547; it has been noted by GNATS.
From: Justin Hawkins <justin@hawkins.id.au>
To: Lars Eggert <lars.eggert@netlab.nec.de>
Cc: freebsd-gnats-submit@FreeBSD.org, lars.eggert@gmx.net
Subject: Re: ports/72547: [PATCH] www/twiki: update to 20040901
Date: Fri, 22 Oct 2004 10:52:31 +0930
On Sat, Oct 16, 2004 at 09:26:06AM +0930, Justin Hawkins wrote:
> On Tue, Oct 12, 2004 at 11:37:53AM +0200, Lars Eggert wrote:
>
> > Very true, as I found out the hard way. Do you have experience with the
> > "upgrade" script that comes with the tarball? I wonder if that could be
> > integrated into "make install."
>
> No I don't - I will investigate and see if it can be feasibly
> integrated.
Yuck - both the manual and the automated upgrade procedures are awful
and pretty un-automatable from a ports perspective.
I'm not seeing a lot of choice here but to flag to the user that an upgrade
requires some manual intervention.
I can't even see a clean path for the manual upgrade, without screwing
up FreeBSD's ports idea of the world (MD5's and so on).
I'll take a look at the postgres port and see if I can do something like it
does, regarding a warning about existing installations before install.
It's actually all really awful, but I guess it's in the nature of
software who's distribution files are expected to be edited in unknown
ways in the normal course of using the software.
- Justin
--
Justin Hawkins | justin@hawkins.id.au
| http://hawkins.id.au
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200410220130.i9M1USBM028914>