From owner-freebsd-ports@FreeBSD.ORG Sat Jan 6 05:15:46 2007 Return-Path: X-Original-To: ports@freebsd.org Delivered-To: freebsd-ports@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id CDDAE16A407 for ; Sat, 6 Jan 2007 05:15:46 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (c220-239-3-125.belrs4.nsw.optusnet.com.au [220.239.3.125]) by mx1.freebsd.org (Postfix) with ESMTP id EF22913C44C for ; Sat, 6 Jan 2007 05:15:45 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by turion.vk2pj.dyndns.org (8.13.8/8.13.8) with ESMTP id l064tJgF012355; Sat, 6 Jan 2007 15:55:19 +1100 (EST) (envelope-from peter@turion.vk2pj.dyndns.org) Received: (from peter@localhost) by turion.vk2pj.dyndns.org (8.13.8/8.13.8/Submit) id l064tIPB012354; Sat, 6 Jan 2007 15:55:18 +1100 (EST) (envelope-from peter) Date: Sat, 6 Jan 2007 15:55:18 +1100 From: Peter Jeremy To: Nick Hilliard Message-ID: <20070106045518.GE839@turion.vk2pj.dyndns.org> References: <200701051612.35209.map@webmatique.com> <459ECABC.90405@foobar.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="84ND8YJRMFlzkrP4" Content-Disposition: inline In-Reply-To: <459ECABC.90405@foobar.org> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.13 (2006-08-11) Cc: ports@freebsd.org Subject: Re: FreeBSD Port: sugarcrm-3.5.1 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: Sat, 06 Jan 2007 05:15:46 -0000 --84ND8YJRMFlzkrP4 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, 2007-Jan-05 22:01:32 +0000, Nick Hilliard wrote: >>However, the freebsd ports system manages upgrades by removing the old=20 >>package, installing the new one, and hoping that the package itself can= =20 >>deal with any sql / config upgrades which might be necessary.=20 =2E.. >>So as maintainer, I'm left with a situation where if a random freebsd=20 >>punter runs "portupgrade" on their sugarcrm installation, they will nuke >> their CRM database. Not optimal. And there is no way in FreeBSD ports >> to detect if the user is running the "portupgrade" command and to bring >> the system to a screeching halt if they try to upgrade sugarcrm by >>using this command.=20 Note that it's not just portupgrade - any similar ports management tool will run into the same problem. And it's not just an issue for sugarCRM - other ports with database backends have similar issues (even portupgrade has been known to upgrade itself into a state where it can't read its own database). The easiest solution I see is for more of the upgrading smarts to move into the core ports system: Add a new "make upgrade" target which defaults to "make uninstall && make install" but can be over-ridden by ports to suit themselves. --=20 Peter Jeremy --84ND8YJRMFlzkrP4 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) iD8DBQFFnyu2/opHv/APuIcRAv6AAJ493H/M7DQNDBezxkFlFxLJjx8FMACfejFU 0t7aWCWGrV/mltguOyD43Co= =/iI1 -----END PGP SIGNATURE----- --84ND8YJRMFlzkrP4--