All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@chromium.org>
To: Simon Glass <sjg@chromium.org>
Cc: 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 14:56:37 -0500	[thread overview]
Message-ID: <CAAbOScnawPZO=NLAJmv2AObchFkjODL+tJrSvc=Keb8=amvYcQ@mail.gmail.com> (raw)
In-Reply-To: <CAPnjgZ3gKxHV7r+WQQOLYh8VioirdCicVAzn62DVfcb-wJ+VxQ@mail.gmail.com>

considering, iiuc, the user has to execute the command to opt-in to
installing the programs, putting it into a dir that's in $PATH is
reasonable

i would quibble that ~/bin is archaic and everyone should be using
~/.local/bin nowadays.  but that can be a followup.
https://specifications.freedesktop.org/basedir-spec/basedir-spec-latest.html
-mike

  reply	other threads:[~2023-02-14 20:11 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 [this message]
2023-02-14 20:08     ` Tom Rini
2023-02-14 20:12       ` Mike Frysinger
2023-02-14 20:27         ` Tom Rini
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='CAAbOScnawPZO=NLAJmv2AObchFkjODL+tJrSvc=Keb8=amvYcQ@mail.gmail.com' \
    --to=vapier@chromium.org \
    --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 \
    /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.