Index | Thread | Search

From:
Stuart Henderson <stu@spacehopper.org>
Subject:
Re: [update] lmdb-1.0.0 (BREAKING CHANGES)
To:
ports@openbsd.org, Aisha Tammy <aisha@openbsd.org>, Rafael Sadowski <rsadowski@openbsd.org>, Kurt Mosiejczuk <kmos@openbsd.org>, Otto Moerbeek <otto@drijf.net>, Antoine Jacoutot <ajacoutot@openbsd.org>
Date:
Fri, 3 Jul 2026 17:25:43 +0100

Download raw body.

Thread
On 2026/07/03 18:11, Jeremie Courreges-Anglas wrote:
> On Fri, Jul 03, 2026 at 04:38:04PM +0100, Stuart Henderson wrote:
> > On 2026/07/03 17:32, Marc Espie wrote:
> > > See what postgresql-server does, there is a WHOLE pkg_add annotation
> > > devoted to it, named @ask-update.
> 
> I had forgotten about ask-update, thanks for pointing it out.
> 
> > > pkg_create(1) has some documentation.
> > > 
> > > Cliff notes:
> > > - in interactive mode it displays a message if the update crosses a version boundary
> > > - it will update in non-interactive mode
> >        ^ will not update in non-interactive mode
> > 
> > however, on 7.9 -> 8.0, you'll be left with a fairly broken set of
> > packages if you deny the update and have py3-lmdb installed.
> 
> OTOH databases/py-lmdb has never been used by the ports tree, so I'm
> not sure how much we should care about it.  Do you remember why you
> imported it?

hmmm, no I don't...and no clues in mystuff. (I care more about the
py3.13->3.14 upgrade path than about py-lmdb, the merge set is
annoyingly fragile).

> Pending some actual migration reports, I'd like to postpone the
> decision of adding @ask-update.  Users could probably also benefit
> from a current.html entry, which could very well be enough given the
> availability of mdb_dump-0.9 in the package and the loud MESSAGE.

makes sense.