On Sat, 8 Apr 2006 09:53:05 +0200 Thierry Thomas <[EMAIL PROTECTED]> wrote:
> Le Ven 7 avr 06 à 16:18:31 +0200, Jeremy Chadwick > <[EMAIL PROTECTED]> é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 reconsider maintainership. -- dick -- http://nagual.st/ -- PGP/GnuPG key: F86289CE ++ Running FreeBSD 6.1 ++ The Power to Serve _______________________________________________ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
