From: Tom Rini <trini@konsulko.com>
To: Mike Frysinger <vapier@chromium.org>
Cc: Simon Glass <sjg@chromium.org>,
Mark Kettenis <mark.kettenis@xs4all.nl>,
u-boot@lists.denx.de, alpernebiyasak@gmail.com, n-francis@ti.com,
stefan.herbrechtsmeier@weidmueller.com,
philippe.reynes@softathome.com, peng.fan@nxp.com
Subject: Re: [PATCH] binman: Avoid requiring a home directory on startup
Date: Tue, 14 Feb 2023 15:27:48 -0500 [thread overview]
Message-ID: <Y+vuxJtkjY9UpSBZ@bill-the-cat> (raw)
In-Reply-To: <CAAbOSck63+=tnmKkWArjVejJcqWWYm9cfkwE9SQLbYSebQeuBQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1279 bytes --]
On Tue, Feb 14, 2023 at 03:12:46PM -0500, Mike Frysinger wrote:
> On Tue, Feb 14, 2023 at 3:08 PM Tom Rini <trini@konsulko.com> wrote:
> > Downloading things from the internet and putting them in to the default
> > PATH always and forever is also kinda not great?
>
> you just described a standard distribution. this is like literally
> how all of them work. not to mention every other language-specific
> distro tool out there (e.g. Python pip, Perl cpan, Go, etc...).
>
> maybe you'd like more guarantees on top (e.g. signature verification)
> which is reasonable.
>
> but to be clear, this script is already merged & in the tree, so your
> feedback doesn't block this patch.
Yes, exactly. This is a fix on top of what we do today, so it should go
in. But modern distributions only install signed packages, and
language-specific tools tend to be a hive of bad examples. Looking over
binman right now, I see that we're either using apt (and oh, there's
"aot" typo in one spot) or downloading from a known Google drive, for
only a few less common tools.
So yes, I would like to see some ideas on how to improve things in the
future so we aren't putting the binaries somewhere that's not a default
(or frequently common) PATH location.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2023-02-14 20:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-10 20:59 [PATCH] binman: Avoid requiring a home directory on startup Simon Glass
2023-02-10 21:23 ` Mark Kettenis
2023-02-14 19:48 ` Simon Glass
2023-02-14 19:56 ` Mike Frysinger
2023-02-14 20:08 ` Tom Rini
2023-02-14 20:12 ` Mike Frysinger
2023-02-14 20:27 ` Tom Rini [this message]
2023-02-17 0:12 ` Simon Glass
2023-02-17 0:19 ` Tom Rini
2023-02-17 2:55 ` Simon Glass
2023-02-17 12:21 ` Quentin Schulz
2023-02-17 23:49 ` Simon Glass
2023-02-20 11:15 ` Quentin Schulz
2023-02-21 19:35 ` Simon Glass
2023-03-08 22:18 ` Simon Glass
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=Y+vuxJtkjY9UpSBZ@bill-the-cat \
--to=trini@konsulko.com \
--cc=alpernebiyasak@gmail.com \
--cc=mark.kettenis@xs4all.nl \
--cc=n-francis@ti.com \
--cc=peng.fan@nxp.com \
--cc=philippe.reynes@softathome.com \
--cc=sjg@chromium.org \
--cc=stefan.herbrechtsmeier@weidmueller.com \
--cc=u-boot@lists.denx.de \
--cc=vapier@chromium.org \
/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.