Mailing-List:	contact cygwin-apps-help AT cygwin DOT com; run by ezmlm
Sender:	cygwin-apps-owner AT cygwin DOT com
List-Subscribe:	<mailto:cygwin-apps-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin-apps/>
List-Post:	<mailto:cygwin-apps AT cygwin DOT com>
List-Help:	<mailto:cygwin-apps-help AT cygwin DOT com>, <http://sources.redhat.com/lists.html#faqs>
Mail-Followup-To:	cygwin-apps AT cygwin DOT com
Delivered-To:	mailing list cygwin-apps AT cygwin DOT com
Message-ID:	<3D1224A6.1010708@ece.gatech.edu>
Date:	Thu, 20 Jun 2002 14:53:26 -0400
From:	Charles Wilson <cwilson AT ece DOT gatech DOT edu>
User-Agent:	Mozilla/5.0 (Windows; U; Win98; en-US; rv:0.9.4) Gecko/20011019 Netscape6/6.2
X-Accept-Language:	en-us
MIME-Version:	1.0
To:	Gareth Pearce <tilps AT hotmail DOT com>
CC:	nwourms AT netscape DOT net, cygwin-apps AT sources DOT redhat DOT com
Subject:	Re: [ITP]: Berkley DB v2
References:	<F18RAKCyyYCkNOYmPSy0002266c AT hotmail DOT com>

Gareth Pearce wrote:

> <note - i know little to nothing about db and havent looked at the 
> packages>
> 
> Hmmm depending on release order seems rather dubious to me...
> Would it not be better to have the symlink installed by postinstall 
> script that checks if there is an existing symlink and only replacing it 
> if the version of the one its pointing too is less then the one being 
> installed?


What if I *want* to revert to an older version?


> same postinstall for all db packages - will work when a new db comes 
> along (assuming that you are using some standard in versioned libs) - 
> and doesnt rely on instalation order (which in my mind sounds sort of 
> easy to break).


Probably.  But the postinstall scripts are all there.  So, you can 
manually re-execute:

/etc/postinstall/libdb3.3-devel.sh.done

and assert the "current" links to the 3.3 version, or 4.0, or whatever.

> (hmmm would need a postuninstall script to chose highest remaining one 
> to link it too as well)


Probably so, but the logic gets tricky.  I think this one can be tabled 
until it becomes an issue.  Under the current scheme, there are two 
fixes if you uninstall (the latest) db-devel:
   1) reinstall (the latest minus one) db-devel
   2) execute /etc/postinstall/libdb(thelatestminusone)-devel.sh.done 
manually.

This will probably be so rare a problem, that I believe these two 
options are sufficient.

--Chuck

- Raw text -