Subject: Re: making 'make replace' safer
To: Peter Schuller <firstname.lastname@example.org>
From: pancake <email@example.com>
Date: 07/17/2006 23:20:49
I've done something similar in shellscript: wip/apstget.
It's not yet finished and needs lot of testing, btw without
caching anything a shellscript calling '$MAKE' is really _slow_.
It have a "relink" action that creates symbolic links to the target
directory to the newest one when a new library is installed.
It works, but ABI problems are not handled. It just allows you
to perform a safe "upgrade" or a package upgrade with relink
libraries on rev dependencies.
It also notifies you about the PKG_OPTIONS flags before starting
So imho the right way to skip the ABI problems is to mark packages
with some kind of abi-version-compatible-range. Or something like
ABI version (btw, it can try to interpret the version number changes
(major number implies completely rebuild of deps). Or something
On Mon, 17 Jul 2006 19:53:05 +0200
Peter Schuller <firstname.lastname@example.org> wrote:
> But not easily. There is no "apt-get dist-upgrade". Hence, on low-priority