Re: Updating graphics/girara and zathura* packages

[Yorick Hardy <yorickhardy%gmail.com@localhost>]

Dear Dave,

On 2026-03-03, Yorick Hardy wrote:
> Dear Dave,
> 
> On 2026-03-02, David H. Gutteridge wrote:
> > On Mon, 2 Mar 2026 at 11:48:19 +0200, Yorick Hardy wrote:
> > > Dear Pkgsrc developers,
> > >
> > > Our girara and zathura packages are a bit out of date, and zathura-
> > pdf-mupdf
> > > currently fails to open pdf files (for me) because of some missing
> > symbols
> > > in the plugin (from libbrotlienc).
> > >
> > > The attached patches attempt to bring all of these packages up to
> > date,
> > > and I have (minimally) tested that each plugin can view a file of the
> > > type it is supposed to support.
> > >
> > > One notable change is that girara no longer depends on gtk3, this
> > dependency
> > > is pushed to zathura (which already depended on gtk3).
> > >
> > > Any opinions on updating these packages (now/later)?
> > > [...]
> > 
> > girara also had an SO major bump, so that means its ABI_DEPENDS
> > should reflect that in buildlinking. I'm not sure if its API
> > also changed in backwards-incompatible ways? I just did a quick pass
> > through and tweaked the buildlink3.mk files for girara and zathura.
> > (Also not sure if there are zathura changes that would create ABI
> > instability?) (I did compile test my changes.)
> > 
> > (The DESCR for girara also seems perhaps out of date now it
> > doesn't use GTK anymore, though I see the upstream doesn't seem to
> > have changed their blurb yet.)
> > 
> > Regards,
> > 
> > Dave
> 
> Thanks for catching that, yes (I also checked girara's page, but
> as you wrote: it still mentions GTK).
> 
> Zathura does not mention API changes in the changelog, but I seem
> to remember having some trouble trying to update plugins only, so
> it may be safer just to assume that the switch to date-versioning
> also needs buildlink3.mk updates.

The last api and abi version bump was in August 2024, for version 0.5.8;
but our update to 0.5.8 did not change our buildlink3.mk. Should we
change it now to 2026.02.22 for both API and ABI?

-- 
Kind regards,

Yorick Hardy