From owner-freebsd-ports@FreeBSD.ORG Tue Aug 30 09:35:02 2005 Return-Path: X-Original-To: freebsd-ports@freebsd.org Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3420116A41F for ; Tue, 30 Aug 2005 09:35:02 +0000 (GMT) (envelope-from boris@brooknet.com.au) Received: from mailout2.pacific.net.au (mailout2.pacific.net.au [61.8.0.115]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9D57743D45 for ; Tue, 30 Aug 2005 09:35:00 +0000 (GMT) (envelope-from boris@brooknet.com.au) Received: from mailproxy2.pacific.net.au (mailproxy2.pacific.net.au [61.8.0.87]) by mailout2.pacific.net.au (8.13.4/8.13.4/Debian-3) with ESMTP id j7U9Ywom011764; Tue, 30 Aug 2005 19:34:58 +1000 Received: from ppp2351.dyn.pacific.net.au (ppp2351.dyn.pacific.net.au [61.8.35.81]) by mailproxy2.pacific.net.au (8.13.4/8.13.4/Debian-3) with ESMTP id j7U9Yttt007065; Tue, 30 Aug 2005 19:34:57 +1000 From: Sam Lawrance To: Nick Hilliard In-Reply-To: <1125326317.49319.31.camel@localhost.netability.ie> References: <1125326317.49319.31.camel@localhost.netability.ie> Content-Type: text/plain Date: Tue, 30 Aug 2005 19:35:08 +1000 Message-Id: <1125394508.791.14.camel@dirk.no.domain> Mime-Version: 1.0 X-Mailer: Evolution 2.2.2 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: freebsd-ports@freebsd.org Subject: Re: Opinions on upgrade process 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: Tue, 30 Aug 2005 09:35:02 -0000 On Mon, 2005-08-29 at 15:38 +0100, Nick Hilliard wrote: > I'm maintainer for deskutils/sugarcrm, which is a pretty cute CRM > application. At the moment, the version in the ports is 2.5.1, which is > relatively old, and it needs to be upgraded. > > Sugar's position on upgrading appears to be that they will only support > upgrading from one specific version to another. So, while sugarcrm > 3.5.0 has now been released, the only way to upgrade your installation > from 2.5.1 is to go 2.5.1 -> 3.0.0 -> 3.0.1x -> 3.5.0. If you don't do > these upgrades in this exact order, you lose your entire customer > database. > > So this means that unless each upgrade is committed to the ports tree, > users are not going to be able to upgrade cleanly from one version to > the next using the freebsd ports collection. On the other hand, Sugar > are pumping out new versions of their product on average every 4 weeks, > which means that people must track the ports collection carefully or > else use date tags to update their ports tree to very specific times so > that they can get the right version. > > The upgrade process looks non trivial in the code - not impossible, but > certainly non trivial. > > Is there any precedent for dealing with this? I.e. install random > versions in the ports and explicitly don't support upgrade? Sugar don't > seem to be particularly responsive to emails (possibly because dealing > with upgrades is hard), so they haven't come back with suggestion on how > to implement an arbitrary upgrade path. > > any suggestions? That's quite a failing on the part of sugarcrm. Even if you go to the trouble of creating an extra two port versions to keep the upgrade path, upgrading would still be ridiculous hassle. IMO the best course of action would be to just bring in 3.5.0 and warn about the incompatibility. If there are problems, people need to raise the issue with sugarcrm so it gets handled.