public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Mike Frysinger" <vapier@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/sandbox:master commit in: src/
Date: Tue,  2 Nov 2021 04:28:17 +0000 (UTC)	[thread overview]
Message-ID: <1635826433.116ca8fd5af908edad85095916585576aa19ec5f.vapier@gentoo> (raw)

commit:     116ca8fd5af908edad85095916585576aa19ec5f
Author:     Mike Frysinger <vapier <AT> gentoo <DOT> org>
AuthorDate: Tue Nov  2 04:13:53 2021 +0000
Commit:     Mike Frysinger <vapier <AT> gentoo <DOT> org>
CommitDate: Tue Nov  2 04:13:53 2021 +0000
URL:        https://gitweb.gentoo.org/proj/sandbox.git/commit/?id=116ca8fd

sandbox: add backwards compat interface hack

Portage runs commands through sandbox like:
  $ sandbox "/usr/lib/portage/python3.9/ebuild.sh unpack"

That means we can't break the CLI without breaking portage and forcing
everyone to upgrade together.  That'll be pretty disruptive for people,
so add a hack to detect this situation: if a single argument is passed
on the CLI, and it doesn't appear to be a file, then fallback to running
it through the shell.  This keeps portage working while allowing the new
interface style to launch.  If/when we can update portage to always use
the -c option, maybe we can drop this in the future.  Or not ... it's
not exactly the worst hack for users.

Bug: https://bugs.gentoo.org/265907
Signed-off-by: Mike Frysinger <vapier <AT> gentoo.org>

 src/sandbox.c | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/src/sandbox.c b/src/sandbox.c
index 2d03dd4..ed0c7f6 100644
--- a/src/sandbox.c
+++ b/src/sandbox.c
@@ -260,6 +260,15 @@ int main(int argc, char **argv)
 		goto oom_error;
 
 	/* Setup bash argv */
+	if (!opt_use_bash && argc == 2) {
+		/* Backwards compatibility hack: if there's only one argument, and it
+		 * appears to be a shell command (not an absolute path to a program),
+		 * then fallback to running through the shell.
+		 */
+		if (access(argv[1], X_OK))
+			opt_use_bash = true;
+	}
+
 	if (opt_use_bash || argc == 1) {
 		str_list_add_item_copy(argv_bash, "/bin/bash", oom_error);
 		str_list_add_item_copy(argv_bash, "-rcfile", oom_error);


             reply	other threads:[~2021-11-02  4:28 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-02  4:28 Mike Frysinger [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-08-08 15:30 [gentoo-commits] proj/sandbox:master commit in: src/ Mike Gilbert
2023-08-05 23:38 Mike Gilbert
2023-08-05 23:38 Mike Gilbert
2021-11-05 10:25 Mike Frysinger
2021-11-05 10:25 Mike Frysinger
2021-11-03  4:55 Mike Frysinger
2021-11-02  4:28 Mike Frysinger
2021-11-01 18:31 Mike Frysinger
2021-10-29  5:37 Mike Frysinger
2021-10-28  9:56 Mike Frysinger
2016-03-29 12:24 Mike Frysinger
2015-09-11  7:53 Mike Frysinger
2015-09-11  7:53 Mike Frysinger

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=1635826433.116ca8fd5af908edad85095916585576aa19ec5f.vapier@gentoo \
    --to=vapier@gentoo.org \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox