Re: USE flag "pdfimport" for binary package "app-office/libreoffice"?

On 5/19/26 11:52 AM, Dr Rainer Woitok wrote:

> And then: checking the runtime dependencies of  "app-office/libreoffice"
> returns among others
> 
>    >=app-text/poppler-22.06:0/158=[cxx]
> 
> a version I installed  at 2022-08-03,  that is,  almost four years back.
> So obviously "app-office/libreoffice" doesn't depend  on the most recent
> "poppler" version.  After using Gentoo for seven years now I'm still far
> from being a Gentoo guru, but Gentoo provides "slots" allowing different
> versions of some package being installed simultaneously.  So couldn't we
> have a "slower" slot of "app-text/poppler" where only those versions are
> provided which fix gross errors and security breaches  and use this slot
> for both,  building "app-office/libreoffice" on the binhost  and running
> it locally?
> 
> Just a thought ...


There are two types of slots. For ">=app-text/poppler-22.06:0/158":

(22.06 is minimum version compatible)

- subslots: ":*/158" is used to trigger recompiles when poppler changes
  ABI

- full slots: ":0/*" is for multiple simultaneous versions


The latter implies that:

/usr/bin/pdfattach

/usr/lib64/libpoppler.so (symlink needed at compile time)

/usr/include/poppler/Page.h

/usr/lib64/pkgconfig/poppler.pc



etc, cannot exist in both packages, so which one should have them?

Full slots require a LOT of work, unless upstream renames all the files.
Full slots are used by things like GCC, which is why /usr/bin/gcc is a
symlink to /usr/x86_64-pc-linux-gnu/gcc-bin/14/x86_64-pc-linux-gnu-gcc
and periodically managed by "eselect gcc".

-- 
Eli Schwartz

-----BEGIN PGP SIGNATURE-----

wnsEABYIACMWIQTnFNnmK0TPZHnXm3qEp9ErcA0vVwUCagyQgwUDAAAAAAAKCRCEp9ErcA0vVzGe
AQDVSNlJcgtoE1izwVRwM9Q4xwMkxS2TlMUOAdGXdNZAbAD+KF0qTys3gH/W4BnydTSI1IZp2rXY
eYvyk/63yadZQw0=
=AFoD
-----END PGP SIGNATURE-----