BEWARE upgrading Horde System
tedm at toybox.placo.com
Sat Apr 8 22:42:37 UTC 2006
Horde is too complex and too configurable a program to
easily fit in the FreeBSD Ports tree. All you can do is
what I think has been done - which is set the port up to
do 90% of the heavy lifting, and depend on the person
doing the installation to finish off the configuration.
I think the horde port met this goal just fine.
It may not be politically correct to say this, but being
able to install and get Horde and IMP and the modules running
either with or without the assistance of the ports directories,
is the mark of a real system administrator. It is, I think,
a given that this port can never meet what I feel is an
unrealistic goal of being able to do a "make install", go away
and come back and have full-blown Horde/IMP server up and
running, ready to use. There's plenty of simpler programs
that the amateurs can do that with and have fine results.
I would point out that even the FreeBSD Release process doesn't
meet this goal. For all the vaunted hype about being able to
type "make release" and build the entire installation CD images,
it is really a bunch of bullshit. "make release" is just the
last command in a very long process of getting the environment
setup, and figuring out what options your going to set and
what they do.
>From: owner-freebsd-questions at freebsd.org
>[mailto:owner-freebsd-questions at freebsd.org]On Behalf Of dick hoogendijk
>Sent: Saturday, April 08, 2006 1:19 AM
>Subject: Re: BEWARE upgrading Horde System
>On Sat, 8 Apr 2006 09:53:05 +0200
>Thierry Thomas <thierry at FreeBSD.org> wrote:
>> Le Ven 7 avr 06 à 16:18:31 +0200, Jeremy Chadwick
>> <freebsd at jdc.parodius.com> écrivait :
>> > On Fri, Apr 07, 2006 at 10:40:01AM +0100, Spadge wrote:
>> > > Why not overwrite the .dist and leave the .conf as it was? OK, so
>> > > it may
>> > Many ports work this way (re: keeping the .conf). The port
>> > maintainer should address this, as many others have done.
>> OK, I must admit that I don't know how to handle properly
>> installation / configuration / deinstallation / reinstallation of the
>> Horde's ports.
>> Since the very first version of these ports, I have tried several
>> solutions and accepted many patches, but I have never found a
>> widespread agreement. Maintainership is now available.
>It won't be me (sadly enough I lack the experience and/or knowledge)
>I *DO* hope however that the horde port will be supported in the future.
>Personally I *never* had any trouble upgrading horde. I *DID* have to
>read the documentation though! It is always needed with horde. But,
>hey, given good docs, that's not too bad, is it?
>Even the latest changes (from 3.0x to 3.1.x) went very very smoothly. I
>just followed the upgrade path (/usr/ports/UPGRADING plus the upgrading
>info from the horde package itself.
>Putting back *.previous files also is not that bad. I can live with it.
>So, I'd like to thank you for all the good work and hope you'd
>dick -- http://nagual.st/ -- PGP/GnuPG key: F86289CE
>++ Running FreeBSD 6.1 ++ The Power to Serve
>freebsd-questions at freebsd.org mailing list
>To unsubscribe, send any mail to
>"freebsd-questions-unsubscribe at freebsd.org"
>No virus found in this incoming message.
>Checked by AVG Free Edition.
>Version: 7.1.385 / Virus Database: 268.4.0/304 - Release Date: 4/7/2006
More information about the freebsd-questions