On Saturday 15 February 2025 05:03:14 Greenwich Mean Time Grant Edwards wrote: > On 2025-02-14, Michael <confabul...@kintzios.com> wrote:
> > This is my profile:
> >
> > ~ $ eselect profile show
> >
> > Current /etc/portage/make.profile symlink:
> > default/linux/amd64/23.0/desktop/plasma
>
> Either that profile or something else you have in your world file
> pulls in qtx11extras as a dependency, so depclean doesn't try to
> remove it.
Yes, my profile specifies plasma and in addition I have installed the kde-
plasma/plasma-meta package which sets USE="qt5". So in my case depclean will
not ask to remove dev-qt/qtx11extras.
> I use the plain 'default/linux/amd64/23.0' profile. Nothing installed
> on my system "depends" on qtx11extras, so depclean wants to remove it
> (as it should).
>
> But libreoffice-bin (which _is_ installed) _uses_ (links to)
> qtx11extras, and depclean was smart enough to detect that and not
> remove qtx11extras (even though nothing on my system "depends" on it).
I don't think libreoffice-bin has a *direct* dependency on qtx11extras, but it
does have a dependency on kde, or gnome. These DEs would drag in their Qt, or
GTK GUI libraries respectively.
> Hence my question: am I correct in my conclusion is that the
> libreoffice-bin ebuild should (but does not) list qtx11extras as a
> dependency?
>
> --
> Grant
As I understand it from the contents of /var/db/repos/gentoo/app-office/
libreoffice-bin/libreoffice-bin-24.2.7.2.ebuild the binary 'flavor' being
fetched and installed from the servers is either kde or gnome specific, with
or without Java. This depends on the kde/gnome/java USE flags set in your
system.
Anyway, it shouldn't be too onerous to test unmerging dev-qt/qtx11extras, then
run 'emerge -t -p -D -v @world' and see what is trying to pull it back in. If
it is libreoffice-bin which asks to rebuild qtx11extras and not some other Qt
or kde package, then this would explain your depclean result and ... confuse
me even more. :-/
Some of the equery results are not 100% representative of the equild contents
and in particular the relationship of conditional dependencies. Regarding
package app-crypt/pinentry graph of conditional dependencies, you can use
qdepend -t -v, e.g.:
~ $ qdepends -t -v app-crypt/pinentry
app-crypt/pinentry-1.3.1:
DEPEND="
>=dev-libs/libassuan-2.1:=
>=dev-libs/libgcrypt-1.6.3
>=dev-libs/libgpg-error-1.17
efl? ( dev-libs/efl[X] )
keyring? ( app-crypt/libsecret )
ncurses? ( sys-libs/ncurses:= )
qt5? (
dev-qt/qtcore:5
dev-qt/qtgui:5
dev-qt/qtwidgets:5
wayland? ( kde-plasma/kwayland:5 )
X? (
dev-qt/qtx11extras:5
x11-libs/libX11
)
)
qt6? (
dev-qt/qtbase:6[gui,widgets]
wayland? (
kde-frameworks/kguiaddons:6
kde-frameworks/kwindowsystem:6
)
)
"
[snip ...]
The above confirms USE="qt5" plus USE="X" is pulling in in dev-qt/qtx11extras
as a dependency for the pinentry package.
signature.asc
Description: This is a digitally signed message part.
