public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Need help with sys-fs/e2fsprogs-1.42.11 build failure
Date: Tue, 05 Aug 2014 06:30:25 -0400	[thread overview]
Message-ID: <1999331.eJvcPo7hDn@vapier> (raw)
In-Reply-To: <CAJ0EP42XaK=JYJrZWxvWoW=u4VnwqYF4ZiV5jmUZGx3ftTZAMA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1747 bytes --]

On Sun 20 Jul 2014 11:12:17 Mike Gilbert wrote:
> On Sun, Jul 20, 2014 at 11:09 AM, Mike Gilbert wrote:
> > 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.
> ---

e2fsprogs-libs was added because it provided those 4 libs which other packages 
were using and people did not like depending on sys-fs/e2fsprogs to get them 
(most significantly libuuid), which is not unreasonable.  since then, 
libuuid/libblkid have moved to util-linux, and the non-linux people again be 
hating on it.  see https://bugs.gentoo.org/278667.

deleting e2fsprogs-libs would busticate them badly.  at least the current 
situation allows us to keep the old version in the tree which provides 
libuuid.

the overhead here is not great imo (having done so for 6 years now), so i 
don't see a problem continuing it.

of course, the libuuid situation needs fixing up properly, but i don't have 
the inclination to sort it out, and the status-quo is still tolerable.

tl;dr: un-fsck the libuuid/libblkid situation and we probably can merge 
e2fsprogs-libs back in.  until then, not really.
-mike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

      parent reply	other threads:[~2014-08-05 10:30 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
2014-07-21  8:47     ` Lars Wendler
2014-08-05 10:30     ` Mike Frysinger [this message]

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=1999331.eJvcPo7hDn@vapier \
    --to=vapier@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