All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 9436] e2fsprogs remove busybox applets even of unselected e2fsprogs components
Date: Mon, 10 Apr 2017 03:44:19 +0000	[thread overview]
Message-ID: <bug-9436-163-dpgLfxg3AD@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-9436-163@https.bugs.busybox.net/>

https://bugs.busybox.net/show_bug.cgi?id=9436

Carlos Santos <casantos@datacom.ind.br> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |WONTFIX
             Status|ASSIGNED                    |RESOLVED

--- Comment #3 from Carlos Santos <casantos@datacom.ind.br> ---
e2fsprogs does not provide an option to disable the build/instalation of chattr
and lsattr, so it is not possible to have "chattr" and "lsattr" from busybox
along with mkfs from e2fsprogs.

So far we attempted to solve the conflicts between busybox and e2fsprogs by
removing busybox programs from /bin and /sbin, leaving the e2fsprogs ones at
/usr/bin and /usr/sbin. This fails with BR2_ROOTFS_MERGED_USR=y, leading to
situations like the one described here. We could provide a better solution by
means of a fine-grained selection of programs, like util-linux does, but this
would require big changes in e2fsprogs.

So instead of resorting to dirty tricks we adopt a pragmatic approach:

1. Drop all configs to select/deselect utilities without corresponding
--enable/disable options to the configure script. In other words, we always
install the basic set of utilities.
2. Do not try to build UUID utilities, since they are disabled along with
libuuid (the util-linux ones must be used instead).
3. Install e2fsprogs utilities at /bin and /sbin, overriding the ones
eventually installed by busybox.

Notice that these changes do exactly the opposite of what is requested. On the
other hand the policy for e2fsprogs becomes coherent with the one for
util-linux: busybox never wins.

Notice that a patch solving several issues related to BR2_ROOTFS_MERGED_USR=y
was submitted for review:

    http://patchwork.ozlabs.org/patch/748826/

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2017-04-10  3:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-19 18:27 [Buildroot] [Bug 9436] New: e2fsprogs remove busybox applets even of unselected e2fsprogs components bugzilla at busybox.net
2016-11-25 20:59 ` [Buildroot] [Bug 9436] " bugzilla at busybox.net
2017-04-02  3:04 ` bugzilla at busybox.net
2017-04-10  3:44 ` bugzilla at busybox.net [this message]
2017-04-11 23:05 ` bugzilla at busybox.net
2017-04-11 23:06 ` bugzilla at busybox.net
2017-05-07 14:08 ` bugzilla at busybox.net
2017-05-08  7:12 ` bugzilla at busybox.net

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=bug-9436-163-dpgLfxg3AD@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@busybox.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.