DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.com;
  h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding;
  b=GwwcplWr9pJF8dmfh3JSP5jE6KBTKLlBhEUzIp+uD4TDDpa1jDj9wVSeGwtrYhVIW2vS0FIk5+3OmaQpN8Bj1cKVCs6BT9rTLNA8oQwhZ/Jp5BxWXRfDLaddfC9UyUo+HzGhOarKkA4Kk6kjkomCpaULlIe16Ru0hUzmqCfUq1s=;
Message-ID: <759731.20927.qm@web130104.mail.mud.yahoo.com>
Date: Sat, 26 Feb 2011 03:36:07 -0800 (PST)
From: Ted Trask <ttrask01@yahoo.com>
Subject: [alpine-devel] Proper way to handle major version upgrade for a package
To: Alpine Developers <alpine-devel@lists.alpinelinux.org>
Precedence: list
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

I have a major version bump for acf-weblog in the works. Unfortunately, it'=
s not =0Abackwards compatible. Since acf-weblog uses postgres, it got me th=
inking about =0Ahow the upgrade from postgres 8 to 9 went. In Alpine Linux =
2.1, we released =0Apostgresql 9.0. Since the data directory moved, a simpl=
e 'apk upgrade' from =0Apostgres 8 to 9=A0broke any=A0existing postgres dat=
abases. There was no real warning =0Afor users. The release notes =0A(http:=
//www.alpinelinux.org/wiki/Release_Notes_for_Alpine_2.1.0) mentioned the =
=0Aversion bump, but nothing about the incompatibility. The only way they w=
ould be =0Aaware of the problem was with insider knowledge about postgres. =
I had several =0Ausers run into this problem.=0A=0AWhat is the proper way t=
o handle upgrades like this?=0A=0A1) Put the upgraded package in a newer ve=
rsion of Alpine Linux (ie 2.2) with a =0Anote in the release notes? Let the=
 user beware.=0A2) Add upgrade instructions to the Alpine release notes? (l=
ike =0Ahttp://www.alpinelinux.org/w/index.php?title=3DTemplate:UpgradeTo2)=
=0A3) Try to create pre/post install scripts to make the upgrade seemless?=
=0A=0AI know option 3 would be a lot of work, considering the number of pac=
kages=A0we =0Anow have,=A0but it's the 'nice' thing to do. Thoughts?=0A=0AT=
ed Trask=0A=0AP.S. Should we go back and try to make the postgres upgrade c=
leaner for future =0Ausers who upgrade to 2.1?=0A=0A=0A      


---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---