From owner-freebsd-ports@FreeBSD.ORG Fri May 27 17:31:16 2011 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 F423E106566C for ; Fri, 27 May 2011 17:31:15 +0000 (UTC) (envelope-from akbeech@gmail.com) Received: from mail-pw0-f54.google.com (mail-pw0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id C2E8F8FC08 for ; Fri, 27 May 2011 17:31:15 +0000 (UTC) Received: by pwj8 with SMTP id 8so1144012pwj.13 for ; Fri, 27 May 2011 10:31:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:from:to:subject:date:user-agent:cc:references :in-reply-to:mime-version:content-type:content-transfer-encoding :message-id; bh=RWOxG2J+jeSEr0dr0LCmYS+jcO1MWYbopIMfStiWTBE=; b=oZbMexdtPsg3nC5R7TyrHpyHR4+u5mi55U8G85FSDjlwJqE9Cl2ivhhbT5vsL4TALO YKxNy54LZdulP5ovewARmr3UI+6z50TXj30Lkuv+RJ+kr8AqV9mwc08M10swnjRiwocM D1IpuXcJYavXYjuegu6OCkE8pKZq+Zf6vKjMI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:subject:date:user-agent:cc:references:in-reply-to :mime-version:content-type:content-transfer-encoding:message-id; b=UvEdBrfEsR4mR4KokZB+A0qaEhuztwbxMpfDi+CR/nPNvU1q5GbN8JzbePIu7GvoIS 7ed2ISkiVCIakjJL7dMxG4/oWnGDM0H8QPG0U/02/jHUXVgL6B24JpRDDKQo1j0RXd6Q HIlQqW71aLiaQe1TJwzyn5jttj8iaR0Af6Zr0= Received: by 10.68.21.33 with SMTP id s1mr866686pbe.510.1306515828355; Fri, 27 May 2011 10:03:48 -0700 (PDT) Received: from maximum3.maximumdata.biz (216-67-98-197.static.acsalaska.net [216.67.98.197]) by mx.google.com with ESMTPS id g1sm54694pbj.51.2011.05.27.10.03.46 (version=SSLv3 cipher=OTHER); Fri, 27 May 2011 10:03:47 -0700 (PDT) From: Beech Rintoul To: freebsd-ports@freebsd.org Date: Fri, 27 May 2011 09:03:44 -0800 User-Agent: KMail/1.13.7 (FreeBSD/9.0-CURRENT; KDE/4.6.3; i386; ; ) References: <20110526105815.10916x8yepdlsilj@webmail.leidinger.net> <201105260804.28523.beech@freebsd.org> <20110527093630.16964k7jvut32j5q@webmail.leidinger.net> In-Reply-To: <20110527093630.16964k7jvut32j5q@webmail.leidinger.net> MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: 7bit Message-Id: <201105270903.44438.akbeech@gmail.com> Cc: Alexander Leidinger Subject: Re: State of affairs with Horde4 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: Fri, 27 May 2011 17:31:16 -0000 On Thursday 26 May 2011 23:36:30 Alexander Leidinger wrote: > Quoting Beech Rintoul (from Thu, 26 May 2011 > > 08:04:28 -0800): > > On Thursday 26 May 2011 00:58:15 you wrote: > >> Hi, > >> > >> I've seen your commits to horde4. I would like to know that current > >> status of this. Are there still some things to do, or is your > >> update-work finished in ports? > >> > >> If there are no open issues anymore, did you replace a horde3 (imp, > >> kronolith, nag, turba, ...) install with horde4? If yes, was it an > >> update and how did it went, or was it a complete new setup? > > > > There is still much to do with horde4. This series completely replaces > > any previous versions and isn't backwards compatible with any other > > horde framework. Horde decided to go with pear install and split > > everything into approx 70 separate installs. That's a work in progress > > to translate all those libs and extensions into FreeBSD's port system. > > If you want to try it in the meantime, you can do a pear install -a -B > > of any of the apps and it will install everything into ${PEARDIR}/horde. > > Both that path and > > ${PREFIX}/www/horde are in the search path, so you can have both until I > > get everything ported. > > I would prefer to install via ports instead via pear. Do you have any > idea about your available time for this (= when do you plan to finish > this.. I mostly care about IMP/kronolith/nag/turba and maybe mnemo, I > do not care much about hermes and whups (I have them installed but I > do not really use them))? I'm going to be working on this mostly full time till it's done. My boss wants all this for our company, so excluding an emergency I have the green light to concentrate on this project. It's still too early to give an estimate on finishing but unless I run into something show stopping I should have this done in a few more days. Hermes and whups aren't ported to H4 yet, so I'm not sure they'll work. Everything else you mentioned is available. I'm still working on the base dependencies and hope to have everything (meaning framework & imp) in by the end of the weekend ${REALJOB} permitting. > > > I haven't seen any major problems with this release apart from the normal > > config issues. Horde has never been much fun to configure given all the > > choices, but watching the lists I'm only seeing minor problems and they > > seem very good about addressing same. My experience is with a new > > install, but migration is possible and supported. I would definitely > > back up your db before > > even attempting an upgrade. The db schema updates are now all > > contained inside > > the main configure screen, but the docs on updating are still sketchy. > > I already read the availabe docs regarding the migration before I > contacted you. Taking a ZFS snapshot before the upgrade is the first I > plan to do when I try to migrate. > > > H3 is still fully supported and I plan on keeping it updated. This > > new release > > is such a huge departure from previous versions that there really aren't > > any choices besides a fresh install (keeping the old data and > > importing). > > > > I would much appreciate any feedback you have if you do update to this > > version. > > Ok, give me (and/or ports) a heads-up when you have the ports in a > state you feel good about, and I try to get some time to upgrade and > tell about my experience. I hit a snag with both migration and locale which "pear install" to ${PEARDIR}/data/horde. Hopefully I can just install those files into www/horde/data and have the correct path without too much hacking. I would really like to avoid having these ports all spread out on the system. I plan to keep everyone posted and will put an entry in UPDATING when I get everything playing nicely. Everything I've committed so far works, but may not be complete. Beech