Subject: Re: OpenSSL upgrade does not bump minor version of shared libs
To: Olaf Seibert <firstname.lastname@example.org>
From: Alistair Crooks <email@example.com>
Date: 04/26/2001 16:59:05
On Thu, Apr 26, 2001 at 05:54:57PM +0200, Olaf Seibert wrote:
> On Thu 26 Apr 2001 at 10:18:57 -0500, Frederick Bruckman wrote:
> > Well, FORCE_PKG_REGISTER leaves a mess, but you must know that, of
> > course.
> I do, and I've had to clean it up already a few times I think. It is
> kind of useful if you want to keep older versions of shared libs around
> when you don't want to recompile "everything", and that sort of thing.
> > I'd recommend that you reinstall the binary packages that you
> > thoughtfully made and saved when you built and installed the packages.
> > (Too late?)
> I've been looking for an easy way to do it later, yes. Binary packages
> often seems to require just a bit more than is saved in /var/db/pkg or
> is given in the pkgsrc directory. It would be acceptable if a full
> recompilation is required, but "package" depends on "install" and
> actually uses something that is built then, and I discovered that faking
> it is not (always) easy/possible. Or maybe I just didn't look far
> enough. And anyway it's been a while and I have forgotten the exact
> details already and it may be different now anyway...
> Anyway, making a binary package out of just an installed package could
> also be useful for including local configuration.
pkgsrc/pkgtools/pkg_tarup will build a binary package from an installed