Public SourceMage Discussion List

[Ismael Luceno <ismael.luceno AT gmail.com>]

On 05/Aug/2017 09:51, Remko van der Vossen wrote:
> On Fri, Aug 04, 2017 at 06:47:03PM -0700, Eric Sandall wrote:
> > On 8/4/17 5:45 AM, Thomas Orgis wrote:
> > > Am Thu, 3 Aug 2017 18:08:41 -0700
> > > schrieb Eric Sandall <eric AT sandall.us>: 
> > >
> > >> How did those of you on test grimoire get past Bug 16031-
> > >> <https://bugs.sourcemage.org/show_bug.cgi?id=16031><https://bugs.sourcemage.org/show_bug.cgi?id=16031>Cannot
> > >> upgrade from stable 0.62-10 to test 0.63 due to gmp 4.3.2 -> 6.1.2
> > >> update <https://bugs.sourcemage.org/show_bug.cgi?id=16031> ? 
> > > Thanks for pointing that out. Glad that I didn't jump into that yet. As
> > > discussed recently with the ncurses6 jump, we really, really need at
> > > least library preservation for these cases. Some sorcery support to
> > > remove the respective library files from the install log of gmp/ncurses
> > > before dispel and put them into a list. Or create local spells for the
> > > vintage version to dispel after all dependers got rebuild.
> > >
> > > Any ABI break like that needs to be handled. Currently, there is only
> > > manual workarounds, like Pol did with ncurses locally.
<...>
> In my opinion we need to be able to "split" a spell into a reduced
> original and a preservation spell that "owns" the legacy shared objects.
> The preservation spell should have a mechanism to prevent dispelling
> until all dependees on the old shared object have been upgraded or
> removed.

+1. That would be the best solution.

Now, I wonder how much work would it be to allow more than one version
to be installed, that too would solve our problem.