Summary: | gnome-base/gvfs: fix udev dependencies | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | William Hubbs <williamh> |
Component: | Current packages | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | candrews, edt, sping, transacid |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 348472 | ||
Attachments: | updated ebuild for gvfs 1.6.7 |
Description
William Hubbs
![]() Created attachment 276285 [details]
updated ebuild for gvfs 1.6.7
I was able to build the attached ebuild with only this change:
udev? (
cdda? ( >=dev-libs/libcdio-0.78.2[-minimal] )
|| ( >=sys-fs/udev-145[extras] >=sys-fs/udev-171 ) )
I did not have to require any use flags. However, some other ebuilds required gudev, and so I was forced to use gudev too.
# echo sys-fs/udev gudev >> /etc/portage/package.use
gudev may be required here too. It's hard for me to tell.
FWIW, Here's how I built udev: [ebuild R ~] sys-fs/udev-171-r1 USE="acl gudev rule_generator -action_modeswitch -debug -edd -floppy -hwdb (-introspection) -keymap (-selinux) -test" 0 kB (In reply to comment #1) > > udev? ( > cdda? ( >=dev-libs/libcdio-0.78.2[-minimal] ) > || ( >=sys-fs/udev-145[extras] >=sys-fs/udev-171 ) ) Again, if gudev is correct, the dependency should look like this: || ( >=sys-fs/udev-171[gudev] >=sys-fs/udev-145[extras] ) ) Maintainers, is gudev the correct flag? If so I am willing to make the changes myself. gudev is needed, see configure.ac. I dared touch this myself: + 09 Jun 2011; Sebastian Pipping <sping@gentoo.org> gvfs-1.6.7.ebuild: + Add >=sys-fs/udev-171[gudev] as an alternative dependency to + >=sys-fs/udev-145[extras] (bug #370353) + Closing, please re-open as needed. @sping, please let gnome herd handle its packages unless otherwise told as we generally take care of synchronizing overlay with gentoo-x86 changes. *** Bug 370737 has been marked as a duplicate of this bug. *** |