From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4] mtree: new package
Date: Thu, 28 Mar 2019 22:53:05 +0100 [thread overview]
Message-ID: <20190328225305.174d234e@windsurf> (raw)
In-Reply-To: <87ef6qlnow.fsf@dell.be.48ers.dk>
On Thu, 28 Mar 2019 21:59:59 +0100
Peter Korsgaard <peter@korsgaard.com> wrote:
> > I'm fine with this as well. It means we would no longer support glibc
> > 2.19 anymore.
>
> Didn't you just last month argue against removing support for glibc <
> 2.19 support (the runc security fix):
In fact, my last sentence lacked an ending question mark. I wanted to
ask if we were dropping support entirely for glibc 2.19, or just saying
"glibc 2.19 is not long important enough to worry too much about it,
especially when it's just for the few packages that use the <fts.h>
interface".
But if your point is to have me say that I don't have a clear and
well-defined opinion, then yes it's the case. I do see a number of
companies/customers continue to use old toolchains and therefore
dropping support too quickly tends to be annoying. On the other side,
we clearly see the maintenance burden that keeping support for old
toolchains creates.
> I don't have a problem dropping support for ancient toolchains when they
> add too much complexity, but the lack of large file support is mtree is
> probably not really reason enough.
So, what do you suggest ? What I proposed with the hidden option ?
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-03-28 21:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-26 14:24 [Buildroot] [PATCH v4] mtree: new package Esben Haabendal
2019-03-27 19:18 ` Thomas Petazzoni
2019-03-27 22:28 ` Esben Haabendal
2019-03-28 11:14 ` Thomas Petazzoni
2019-03-28 15:14 ` Esben Haabendal
2019-03-28 18:13 ` Arnout Vandecappelle
2019-03-28 20:00 ` Thomas Petazzoni
2019-03-28 20:59 ` Peter Korsgaard
2019-03-28 21:53 ` Thomas Petazzoni [this message]
2019-03-29 9:31 ` Arnout Vandecappelle
2019-03-29 9:35 ` 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=20190328225305.174d234e@windsurf \
--to=thomas.petazzoni@bootlin.com \
--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