From: Peter Korsgaard <peter@korsgaard.com>
To: Marcus Hoffmann <buildroot@bubu1.eu>
Cc: yann.morin@orange.com,
James Hilliard <james.hilliard1@gmail.com>,
buildroot@buildroot.org,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Thomas Perale <thomas.perale@mind.be>,
Ricardo Martincoski <ricardo.martincoski@datacom.com.br>
Subject: Re: [Buildroot] minimum system/coreutils requirements
Date: Thu, 18 Jun 2026 16:27:05 +0200 [thread overview]
Message-ID: <87qzm3exfq.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <9b0c655b-ff65-4841-9390-43515fb06d56@bubu1.eu> (Marcus Hoffmann's message of "Thu, 18 Jun 2026 16:04:42 +0200")
>>>>> "Marcus" == Marcus Hoffmann <buildroot@bubu1.eu> writes:
Hello,
> James already sent a version which does that and it seems okay to
> merge if anyone actually needs this on old versions.
> It's not super great though because if someone where to add a blake2b
> hash for a non-python package which then someone would try to build on
> an old distro it would still break, I think?
> I guess I'd mostly like to know if this complexity is actually worth
> it and if we would want to at least define a minimum supported
> coreutils version which we could bump at some point to get rid of
> these checks again.
> Opinions?
I would not be against just requiring b2sum on the build host. This is
presumably not a feature we would want to backport to 2025.02.x, so
"enterprise" users will most likely only run into it when moving to
2027.02.x.
In Debian terms, coreutils 8.26 was included in Debian 9 which was
released 2017/06/17 and will go out of ELTS support on 2027/06/30, so it
is not a suitable distribution to use for the duration of our 2027.02.x
anyway.
I think time has also come to drop the check for realpath / relative ln.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2026-06-18 14:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-17 17:42 [Buildroot] [PATCH v2 1/3] support/download: add blake2b-256 hash support James Hilliard
2026-06-17 17:42 ` [Buildroot] [PATCH v2 2/3] package/pkg-python: derive PyPI site from blake2b-256 hash James Hilliard
2026-06-17 17:42 ` [Buildroot] [PATCH v2 3/3] package/python-async-timeout: use hash-based PyPI site James Hilliard
2026-06-18 5:51 ` [Buildroot] [PATCH v2 1/3] support/download: add blake2b-256 hash support yann.morin
2026-06-18 14:04 ` [Buildroot] minimum system/coreutils requirements (was: support/download: add blake2b-256 hash support) Marcus Hoffmann via buildroot
2026-06-18 14:27 ` Peter Korsgaard [this message]
2026-06-18 14:59 ` yann.morin
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=87qzm3exfq.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@bubu1.eu \
--cc=buildroot@buildroot.org \
--cc=james.hilliard1@gmail.com \
--cc=ricardo.martincoski@datacom.com.br \
--cc=thomas.perale@mind.be \
--cc=thomas.petazzoni@bootlin.com \
--cc=yann.morin@orange.com \
/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