Summary: | app-cdr/k3b - Depend on app-admin/eselect-cdparanoia. | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Roman Gruber <roman.gruber> |
Component: | Current packages | Assignee: | Gentoo KDE team <kde> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | media-optical, tomwij |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Roman Gruber
2013-01-19 11:38:34 UTC
nope, nothing should depend on eselect-cdparanoia since cdparanoia itself and libcdio-paranoia itself already depends on it and pulls it in Unmerge =media-sound/cdparanoia-3.10.2-r4::gentoo and then emerge k3b again. I've tried to replicate this on my system (both eselect and non-eselect properly installed) as well as on a test chroot environment (both not installed); works for me. From this testing I can conclude that your k3b dependency tree might have reached an incorrect state while these changes were applied, past and future users should not experience this issue as far as I can see. If k3b only uses the `cdparanoia` executable, then you would be right in sense that the depend should be: || ( media-sound/cdparanoia dev-libs/libcdio-paranoia ) But if it's linking against lib from cdparanoia, then it shouldn't be that, but it should just depend directly on cdparanoia. I don't know which one it is for k3b. Reopen if you are absolutely sure it only needs the cdparanoia executable. You can run something like: emerge -1 cdparanoia emerge k3b qlist k3b | xargs objdump -p |grep NEEDED if you see libs from the cdparanoia package in that output, it directly uses cdparanoia libs... maintainers? reporter? someone reopen after checking if required |