| 1 |
On Monday, 24 June 2019 01:12:07 BST Neil Bothwick wrote: |
| 2 |
> On Sun, 23 Jun 2019 23:35:33 +0100, Peter Humphrey wrote: |
| 3 |
> > > > Why isn't device-mapper it's own package‽ One which LVM depends |
| 4 |
> > > > on. |
| 5 |
> > > |
| 6 |
> > > No idea, but I'd guess it's got something to do with not reinventing |
| 7 |
> > > the wheel. From a maintenance point of view, a USE flag would be less |
| 8 |
> > > effort than two packages. |
| 9 |
> > > |
| 10 |
> > > > Multi-Path (as in dm-multipath) can easily be used without LVM. |
| 11 |
> > > |
| 12 |
> > > Which is why the USE flag exists, to avoid installing LVM. |
| 13 |
> > |
| 14 |
> > But it's not supported. |
| 15 |
> |
| 16 |
> In what way. I've just tried emerging lvm2 with USE="device-mapper-only |
| 17 |
> -thin" and it installed the device-mapper stiff but none of the lvm |
| 18 |
> executables, which seems to be exactly what is wanted. |
| 19 |
|
| 20 |
use.local.desc:sys-fs/lvm2:device-mapper-only - Build only device-mapper and |
| 21 |
not the rest of LVM2 (UNSUPPORTED) |
| 22 |
|
| 23 |
-- |
| 24 |
Regards, |
| 25 |
Peter. |
Archives