Am Di, 11 Jun 2024 13:28:52 +0200
schrieb Chris Hofstaedtler <z...@debian.org>:
> On Tue, Jun 11, 2024 at 01:04:06PM +0200, Julian Wollrath wrote:
> > > > Specifically, the problem is that
> > > > debian/libjxl-gdk-pixbuf.postinst and
> > > > debian/libjxl-gdk-pixbuf.postrm have hardcoded the amd64
> > > > architecture which means that libjxl-gdk-pixbuf is
> > > > uninstallable on architectures other than amd64.
> > >
> > > Could you comment on the above ?
> >
> > hmm, in principle that utility should be called, to make gdk-pixbuf
> > aware of the jpeg-xl loader. Maybe a workaround would be to have
> > $ cat libjxl-gdk-pixbuf.postinst
> > #!/bin/sh -e
> > for X in /usr/lib/*/gdk-pixbuf-2.0/gdk-pixbuf-query-loaders
> > do
> > if [ -x ${X} ]; then
> > ${X} --update-cache
> [..]
>
> > instead? And for libjxl-gdk-pixbuf.postrm this should also work. Or
> > is there a better way, to get the library triplet for the
> > architecture of the packet, that is being installed?
>
> https://manpages.debian.org/bookworm/debhelper/dh_installdeb.1.en.html#SUBSTITUTION_IN_MAINTAINER_SCRIPTS
> documents which tokens are available at build time to generate the
> maintscripts.
Thanks. So the path to the binary would be
/usr/lib/#DEB_TARGET_MULTIARCH#/gdk-pixbuf-2.0/gdk-pixbuf-query-loaders
>
> I've CCed smcv@, as I think there is a better way than running a
> postinst script in each individual package (triggers?). Maybe smcv
> can chime in here.
Agreed, seeing, that this is not the only available loader, a more
generic way could be cleaner.
Cheers,
Julian
>
> Chris
>
--
() ascii ribbon campaign - against html e-mail
/\ - against proprietary attachments
