| 1 |
On Sat, Aug 23, 2014 at 1:47 AM, Alexander Kapshuk |
| 2 |
<alexander.kapshuk@×××××.com> wrote: |
| 3 |
> On 08/22/2014 10:36 PM, Canek Peláez Valdés wrote: |
| 4 |
>> On Fri, Aug 22, 2014 at 1:56 PM, Alexander Kapshuk |
| 5 |
>> <alexander.kapshuk@×××××.com> wrote: |
| 6 |
>>> As I updated my system today, I noticed that 'sys-fs/lvm2' got updated |
| 7 |
>>> amongst other packages as well. |
| 8 |
>>> |
| 9 |
>>> I don't use LVM on my system. |
| 10 |
>>> |
| 11 |
>>> If I understand it correctly, 'sys-fs/lvm2' is a required dependency for |
| 12 |
>>> 'sys-fs/udisks/udisks-1.0.5-r1': |
| 13 |
>>> |
| 14 |
>>> equery d sys-fs/lvm2 |
| 15 |
>>> * These packages depend on sys-fs/lvm2: |
| 16 |
>>> sys-block/parted-3.1-r1 (device-mapper ? >=sys-fs/lvm2-2.02.45) |
| 17 |
>>> sys-boot/grub-2.00_p5107-r2 (device-mapper ? >=sys-fs/lvm2-2.02.45) |
| 18 |
>>> sys-fs/udisks-1.0.5-r1 (>=sys-fs/lvm2-2.02.66) |
| 19 |
>>> sys-fs/udisks-2.1.3 (cryptsetup ? sys-fs/lvm2[udev(+)]) |
| 20 |
>>> |
| 21 |
>>> equery -q u sys-block/parted | grep device-mapper |
| 22 |
>>> -device-mapper |
| 23 |
>>> |
| 24 |
>>> equery -q u sys-boot/grub | grep device-mapper |
| 25 |
>>> -device-mapper |
| 26 |
>>> |
| 27 |
>>> equery -q u '=sys-fs/udisks-1.0.5-r1' |
| 28 |
>>> -debug |
| 29 |
>>> +nls |
| 30 |
>>> -remote-access |
| 31 |
>>> |
| 32 |
>>> $ equery -q u '=sys-fs/udisks-2.1.3' | grep cryptsetup |
| 33 |
>>> -cryptsetup |
| 34 |
>>> |
| 35 |
>>> /usr/portage/sys-fs/udisks/udisks-1.0.5-r1.ebuild:17,24 |
| 36 |
>>> COMMON_DEPEND=">=dev-libs/dbus-glib-0.100 |
| 37 |
>>> <snip> |
| 38 |
>>> >=sys-fs/lvm2-2.02.66 |
| 39 |
>>> |
| 40 |
>>> What are my options, if I were to remove 'sys-fs/lvm2' altogether? |
| 41 |
>> Remove sys-fs/udisks:0, which depends unconditionally on LVM2; also, |
| 42 |
>> it's on life support, AFAIR. sys-fs/udisks:2 is actively maintained |
| 43 |
>> and it depends only conditionally on LVM2. |
| 44 |
>> |
| 45 |
>>> What would you recommend doing about it? |
| 46 |
>> What does depend on sys-fs/udisks? What's the output from "equery d |
| 47 |
>> sys-fs/udisks"? Most applications switched to udisks-2, but some are |
| 48 |
>> still stuck with udisks-1 (XMBC, now Kodi, comes to mind). |
| 49 |
>> |
| 50 |
>> If an application that you absolutely need requires sys-fs/udisks:0, |
| 51 |
>> then you will need LVM2 also. |
| 52 |
>> |
| 53 |
>> Regards. |
| 54 |
> |
| 55 |
> Looks like I've got a couple of apps that do require udisks-1 to run: |
| 56 |
> equery d sys-fs/udisks |
| 57 |
> * These packages depend on sys-fs/udisks: |
| 58 |
> gnome-base/gvfs-1.20.2 (udisks ? >=sys-fs/udisks-1.97:2) |
| 59 |
|
| 60 |
gvfs depends on sys-fs/udisk:2, so this one doesn't need udisks-1. |
| 61 |
|
| 62 |
> xfce-extra/xfce4-power-manager-1.3.0 (udisks ? sys-fs/udisks:0) |
| 63 |
|
| 64 |
What does xfce4-power-manager uses udisks for? You could try to emerge |
| 65 |
it with USE="-udisks" and see if you miss some functionality. If you |
| 66 |
don't, you can get rid of udisks-1 and LVM2. |
| 67 |
|
| 68 |
Regards. |
| 69 |
-- |
| 70 |
Canek Peláez Valdés |
| 71 |
Profesor de asignatura, Facultad de Ciencias |
| 72 |
Universidad Nacional Autónoma de México |
Archives