On Sunday 05 Mar 2017 02:10:09 Alon Bar-Lev wrote:
> It was tested, otherwise how could the conflict with kde-apps/gpgmepp
> and kde-apps/kdepimlibs:4 been known?
Think of it from my point of view. I followed the official guide to
installing a stable KDE system on a plasma profile. I don't have any odd
extras, omissions or other departures from the ordinary KDE experience. The
only other program I run is BOINC (whence the wxGTK webkit USE flag below).
I didn't make any USE changes except what was necessary to get the system
working. Here is the entirety of my USE flags:
# make.conf:
USE="-bluetooth -btrfs -fortran -gcj -geoloc -geolocation -gnome -iodbc
-ldap -lirc -nis -odbc -systemd -thin -wifi -wireless -xinerama
gpm handbook icu symlink"
# package.use:
app-emulation/virtualbox additions extensions java python
dev-lang/python sqlite
kde-apps/kdesu -handbook
media-libs/libvpx svc
media-libs/mesa -vaapi
net-misc/iputils -caps -filecaps
sys-devel/llvm clang video_cards_radeon
sys-kernel/linux-firmware savedconfig
x11-libs/libdrm video_cards_radeon
x11-libs/wxGTK webkit
That must be as close as can be to "standard", surely.
I use KMail but not the rest of kde-pim.
Now tell me why I should expect to be thrown a wobbler like a dependency
conflict that cannot be resolved, on the face of it, and not at all without
what look like significant system changes.
By the way, I did check for bugs before posting the first time, but I didn't
expect to find anything useful in a stabilisation request - I never have
before - so I didn't look at it. Mea culpa to that extent.
--
Regards
Peter
