Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Carlos Santos <casantos@datacom.ind.br>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] e2fsprogs: keep util-linux's fsck if chosen
Date: Mon, 21 Nov 2016 13:03:11 -0200 (BRST)	[thread overview]
Message-ID: <621304273.6901494.1479740590995.JavaMail.zimbra@datacom.ind.br> (raw)
In-Reply-To: <CAGduivxBL8=fZafQG3odT_2_UUDruUgB1ioozn9tJvX6OPe_Zw@mail.gmail.com>

> From: "Maxime Hadjinlian" <maxime.hadjinlian@gmail.com>
> To: "Carlos Santos" <casantos@datacom.ind.br>
> Cc: "buildroot" <buildroot@buildroot.org>
> Sent: Monday, November 21, 2016 12:24:07 PM
> Subject: Re: [Buildroot] [PATCH 2/2] e2fsprogs: keep util-linux's fsck if chosen

> Hi there,
> 
> On Mon, Nov 21, 2016 at 2:10 PM, Carlos Santos <casantos@datacom.ind.br> wrote:
>>> From: "Maxime Hadjinlian" <maxime.hadjinlian@gmail.com>
>>> To: buildroot at buildroot.org
>>> Sent: Friday, November 18, 2016 1:24:27 PM
>>> Subject: [Buildroot] [PATCH 2/2] e2fsprogs: keep util-linux's fsck if chosen
>>
>>> Since e2fsprogs depends on util-linux, it's build after it. It means
>>> that if you want the fsck wrapper from util-linux (which is better
>>> maintained and you are sure that it's compatible with systemd) and you
>>> want e2fsck, it won't work.
>>>
>>> Because of the merge of /usr/bin and /bin, we end up deleting the fsck
>>> from util-linux.
>>>
>>> This makes an attempt at fixing the issues.
>>>
>>> Signed-off-by: Maxime Hadjinlian <maxime.hadjinlian@gmail.com>
>>> ---
>>> I am cleary not satisfied by the way I handled that, I am not even sure
>>> it works in all cases. I can't spend much more time on this right now,
>>> so I need advice/help from the community to fix that in a proper/generic
>>> manner.
>> What about using something like this, instead?
> It's indeed better, but you have to keep the bit about the busybox
> applet due to the merge of /sbin and /usr/sbin

Right. Looks like combining the changes in Config.in and e2fsprogs.mk is the best approach.

>>
>> diff --git a/package/e2fsprogs/Config.in b/package/e2fsprogs/Config.in
>> index 4db11e1..c0b48e1 100644
>> --- a/package/e2fsprogs/Config.in
>> +++ b/package/e2fsprogs/Config.in
>> @@ -60,8 +60,12 @@ config BR2_PACKAGE_E2FSPROGS_FILEFRAG
>>
>>  config BR2_PACKAGE_E2FSPROGS_FSCK
>>         bool "fsck"
>> +       depends on !BR2_PACKAGE_UTIL_LINUX_FSCK
>>         default y
>>
>> +comment "the fsck from util-linux has preference over this one"
>> +       depends on BR2_PACKAGE_UTIL_LINUX_FSCK
>> +
>>  config BR2_PACKAGE_E2FSPROGS_FUSE2FS
>>         bool "fuse2fs"
>>         depends on !BR2_STATIC_LIBS # libfuse
>>
>>
>> Carlos Santos (Casantos)
>> DATACOM, P&D

  reply	other threads:[~2016-11-21 15:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-18 15:24 [Buildroot] [PATCH 1/2] e2fsprogs: propagate LDCONFIG=true Maxime Hadjinlian
2016-11-18 15:24 ` [Buildroot] [PATCH 2/2] e2fsprogs: keep util-linux's fsck if chosen Maxime Hadjinlian
2016-11-21 13:10   ` Carlos Santos
2016-11-21 14:24     ` Maxime Hadjinlian
2016-11-21 15:03       ` Carlos Santos [this message]
2017-03-27 21:29         ` Arnout Vandecappelle
2017-03-27 21:31           ` Arnout Vandecappelle
2016-12-11 15:02 ` [Buildroot] [PATCH 1/2] e2fsprogs: propagate LDCONFIG=true Thomas Petazzoni

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=621304273.6901494.1479740590995.JavaMail.zimbra@datacom.ind.br \
    --to=casantos@datacom.ind.br \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox