1 |
On Sun, Jul 20, 2014 at 11:09 AM, Mike Gilbert <floppym@g.o> wrote: |
2 |
> On Sun, Jul 20, 2014 at 6:47 AM, Lars Wendler <polynomial-c@g.o> wrote: |
3 |
>> Hi guys, |
4 |
>> |
5 |
>> I just add e2fsprogs{,-libs}-1.42.11 |
6 |
> |
7 |
> Is there some reason that we continue to maintain these as two |
8 |
> separate packages? It seems like the e2fsprogs ebuild could |
9 |
> build/install both the binaries and the libraries, and that would |
10 |
> probably prevent weird failures like this one. |
11 |
> |
12 |
> I see this in README.subset: |
13 |
|
14 |
Oops, hit send too quickly. |
15 |
|
16 |
I see this in README.subset: |
17 |
|
18 |
--- |
19 |
This distribution contains a subset of the e2fsprogs package; it |
20 |
contains the base libraries (ss, et, uuid, blkid) which may be used by |
21 |
other non-ext2-related applications. |
22 |
|
23 |
This may be useful for non-Linux operating systems that need these |
24 |
libraries for GNOME, but who do not need the ext2/ext3 filesystem |
25 |
utilities. |
26 |
--- |
27 |
|
28 |
From what I can tell, e2fsprogs and e2fsprogs-libs have mostly the |
29 |
same KEYWORDS with a couple of exceptions: |
30 |
|
31 |
x86-fbsd |
32 |
x86-freebsd |
33 |
x86-solaris |
34 |
|
35 |
It hardly seems worth the effort to maintain 2 ebuilds for these small |
36 |
platforms. |