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 v2] e2fsprogs: keep util-linux's fsck if	chosen
Date: Sun, 2 Apr 2017 11:38:26 -0300 (BRT)	[thread overview]
Message-ID: <408746197.17288398.1491143906343.JavaMail.zimbra@datacom.ind.br> (raw)
In-Reply-To: <1429239756.17288393.1491143437663.JavaMail.zimbra@datacom.ind.br>

> From: "Carlos Santos" <casantos@datacom.ind.br>
> To: "Maxime Hadjinlian" <maxime.hadjinlian@gmail.com>
> Cc: "buildroot" <buildroot@buildroot.org>
> Sent: Sunday, April 2, 2017 11:30:37 AM
> Subject: Re: [Buildroot] [PATCH v2] e2fsprogs: keep util-linux's fsck if	chosen

> like e2fsprogs does. However, util-linux installs fsck unconditionally
> while busybox avoids overriding an existing /sbin/fsck, so their build
> and installation should be irrelevant. A good test is to run

build and installation *order* should be irrelevant

-- 
Carlos Santos (Casantos) - DATACOM, P&D
?The greatest triumph that modern PR can offer is the transcendent 
success of having your words and actions judged by your reputation, 
rather than the other way about.? ? Christopher Hitchens

  reply	other threads:[~2017-04-02 14:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-02  2:36 [Buildroot] [PATCH v2] e2fsprogs: keep util-linux's fsck if chosen Carlos Santos
2017-04-02 10:13 ` Maxime Hadjinlian
2017-04-02 12:03   ` Carlos Santos
2017-04-02 12:10     ` Maxime Hadjinlian
2017-04-02 14:30       ` Carlos Santos
2017-04-02 14:38         ` Carlos Santos [this message]
2017-04-03 13:16   ` Arnout Vandecappelle

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=408746197.17288398.1491143906343.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