From: Mike Gilbert <floppym@gentoo.org>
To: Gentoo Dev <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] Need help with sys-fs/e2fsprogs-1.42.11 build failure
Date: Sun, 20 Jul 2014 11:12:17 -0400 [thread overview]
Message-ID: <CAJ0EP42XaK=JYJrZWxvWoW=u4VnwqYF4ZiV5jmUZGx3ftTZAMA@mail.gmail.com> (raw)
In-Reply-To: <CAJ0EP404N7=uE0jZiX-W2E+g-4gVVw-L2S-OrM83k8N9Uy-4Qw@mail.gmail.com>
On Sun, Jul 20, 2014 at 11:09 AM, Mike Gilbert <floppym@gentoo.org> wrote:
> On Sun, Jul 20, 2014 at 6:47 AM, Lars Wendler <polynomial-c@gentoo.org> wrote:
>> Hi guys,
>>
>> I just add e2fsprogs{,-libs}-1.42.11
>
> Is there some reason that we continue to maintain these as two
> separate packages? It seems like the e2fsprogs ebuild could
> build/install both the binaries and the libraries, and that would
> probably prevent weird failures like this one.
>
> I see this in README.subset:
Oops, hit send too quickly.
I see this in README.subset:
---
This distribution contains a subset of the e2fsprogs package; it
contains the base libraries (ss, et, uuid, blkid) which may be used by
other non-ext2-related applications.
This may be useful for non-Linux operating systems that need these
libraries for GNOME, but who do not need the ext2/ext3 filesystem
utilities.
---
From what I can tell, e2fsprogs and e2fsprogs-libs have mostly the
same KEYWORDS with a couple of exceptions:
x86-fbsd
x86-freebsd
x86-solaris
It hardly seems worth the effort to maintain 2 ebuilds for these small
platforms.
next prev parent reply other threads:[~2014-07-20 15:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-20 10:47 [gentoo-dev] Need help with sys-fs/e2fsprogs-1.42.11 build failure Lars Wendler
2014-07-20 14:45 ` Mike Gilbert
2014-07-20 14:56 ` Jeroen Roovers
2014-07-20 20:37 ` Lars Wendler
2014-07-20 15:09 ` Mike Gilbert
2014-07-20 15:12 ` Mike Gilbert [this message]
2014-07-21 8:47 ` Lars Wendler
2014-08-05 10:30 ` Mike Frysinger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJ0EP42XaK=JYJrZWxvWoW=u4VnwqYF4ZiV5jmUZGx3ftTZAMA@mail.gmail.com' \
--to=floppym@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox