[bug#34486] [PATCH 0/1] Add '--inherit' to 'guix environment'

[bug#34486] [PATCH 0/1] Add '--inherit' to 'guix environment'

[Ludovic Courtès]

Hello,

This new option allows to specify additional variables to be inherited
in a “pure” (semi-pure?) environment.

The main motivation was the use of the SLURM batch scheduler, which
defines environment variables that you need to preserve so that things
like ‘mpirun’ work correctly.

Thoughts?

Ludo’.

Ludovic Courtès (1):
  environment: Add '--inherit'.

 doc/guix.texi                | 21 ++++++++++++--
 guix/scripts/environment.scm | 53 +++++++++++++++++++++++++-----------
 tests/guix-environment.sh    | 15 +++++++++-
 3 files changed, 69 insertions(+), 20 deletions(-)

-- 
2.20.1

[bug#34486] [PATCH 1/1] environment: Add '--inherit'.

[Ludovic Courtès]

From: Ludovic Courtès <ludovic.courtes@inria.fr>

* guix/scripts/environment.scm (purify-environment): Add 'white-list'
parameter and honor it.
(create-environment): Add #:white-list parameter and honor it.
(launch-environment): Likewise.
(launch-environment/fork): Likewise.
(show-help, %options): Add '--inherit'.
(guix-environment): Define 'white-list' and pass it to
'launch-environment/fork'.
* tests/guix-environment.sh: Test '--inherit'.
* doc/guix.texi (Invoking guix environment): Document it.
---
 doc/guix.texi                | 21 ++++++++++++--
 guix/scripts/environment.scm | 53 +++++++++++++++++++++++++-----------
 tests/guix-environment.sh    | 15 +++++++++-
 3 files changed, 69 insertions(+), 20 deletions(-)

diff --git a/doc/guix.texi b/doc/guix.texi
index 1ac077d98a..68d39ed02f 100644
--- a/doc/guix.texi
+++ b/doc/guix.texi
@@ -4454,9 +4454,24 @@ default behavior.  Packages appearing after are interpreted as packages
 that will be added to the environment directly.
 
 @item --pure
-Unset existing environment variables when building the new environment.
-This has the effect of creating an environment in which search paths
-only contain package inputs.
+Unset existing environment variables when building the new environment, except
+those specified with @option{--inherit} (see below.)  This has the effect of
+creating an environment in which search paths only contain package inputs.
+
+@item --inherit=@var{regexp}
+When used alongside @option{--pure}, inherit all the environment variables
+matching @var{regexp}---in other words, put them on a ``white list'' of
+environment variables that must be preserved.
+
+@example
+guix environment --pure --inherit=^SLURM --ad-hoc openmpi @dots{} \
+  -- mpirun @dots{}
+@end example
+
+This example runs @command{mpirun} in a context where the only environment
+variables defined are @code{PATH}, environment variables whose name starts
+with @code{SLURM}, as well as the usual ``precious'' variables (@code{HOME},
+@code{USER}, etc.)
 
 @item --search-paths
 Display the environment variable definitions that make up the
diff --git a/guix/scripts/environment.scm b/guix/scripts/environment.scm
index 3143ea9281..3966531efa 100644
--- a/guix/scripts/environment.scm
+++ b/guix/scripts/environment.scm
@@ -57,20 +57,27 @@
 (define %default-shell
   (or (getenv "SHELL") "/bin/sh"))
 
-(define (purify-environment)
-  "Unset almost all environment variables.  A small number of variables such
-as 'HOME' and 'USER' are left untouched."
+(define (purify-environment white-list)
+  "Unset all environment variables except those that match the regexps in
+WHITE-LIST and those listed in %PRECIOUS-VARIABLES.  A small number of
+variables such as 'HOME' and 'USER' are left untouched."
   (for-each unsetenv
-            (remove (cut member <> %precious-variables)
+            (remove (lambda (variable)
+                      (or (member variable %precious-variables)
+                          (find (cut regexp-exec <> variable)
+                                white-list)))
                     (match (get-environment-variables)
                       (((names . _) ...)
                        names)))))
 
-(define* (create-environment profile manifest #:key pure?)
-  "Set the environment variables specified by MANIFEST for PROFILE.  When PURE?
-is #t, unset the variables in the current environment.  Otherwise, augment
-existing environment variables with additional search paths."
-  (when pure? (purify-environment))
+(define* (create-environment profile manifest
+                             #:key pure? (white-list '()))
+  "Set the environment variables specified by MANIFEST for PROFILE.  When
+PURE?  is #t, unset the variables in the current environment except those that
+match the regexps in WHITE-LIST.  Otherwise, augment existing environment
+variables with additional search paths."
+  (when pure?
+    (purify-environment white-list))
   (for-each (match-lambda
               ((($ <search-path-specification> variable _ separator) . value)
                (let ((current (getenv variable)))
@@ -133,6 +140,8 @@ COMMAND or an interactive shell in that environment.\n"))
                          of only their inputs"))
   (display (G_ "
       --pure             unset existing environment variables"))
+  (display (G_ "
+      --inherit=REGEXP   inherit environment variables that match REGEXP"))
   (display (G_ "
       --search-paths     display needed environment variable definitions"))
   (display (G_ "
@@ -206,6 +215,11 @@ COMMAND or an interactive shell in that environment.\n"))
          (option '("pure") #f #f
                  (lambda (opt name arg result)
                    (alist-cons 'pure #t result)))
+         (option '("inherit") #t #f
+                 (lambda (opt name arg result)
+                   (alist-cons 'inherit-regexp
+                               (make-regexp* arg)
+                               result)))
          (option '(#\E "exec") #t #f ; deprecated
                  (lambda (opt name arg result)
                    (alist-cons 'exec (list %default-shell "-c" arg) result)))
@@ -397,25 +411,30 @@ and suitable for 'exit'."
 (define primitive-exit/status (compose primitive-exit status->exit-code))
 
 (define* (launch-environment command profile manifest
-                             #:key pure?)
+                             #:key pure? (white-list '()))
   "Run COMMAND in a new environment containing INPUTS, using the native search
 paths defined by the list PATHS.  When PURE?, pre-existing environment
-variables are cleared before setting the new ones."
+variables are cleared before setting the new ones, except those matching the
+regexps in WHITE-LIST."
   ;; Properly handle SIGINT, so pressing C-c in an interactive terminal
   ;; application works.
   (sigaction SIGINT SIG_DFL)
-  (create-environment profile manifest #:pure? pure?)
+  (create-environment profile manifest
+                      #:pure? pure? #:white-list white-list)
   (match command
     ((program . args)
      (apply execlp program program args))))
 
-(define* (launch-environment/fork command profile manifest #:key pure?)
+(define* (launch-environment/fork command profile manifest
+                                  #:key pure? (white-list '()))
   "Run COMMAND in a new process with an environment containing PROFILE, with
 the search paths specified by MANIFEST.  When PURE?, pre-existing environment
-variables are cleared before setting the new ones."
+variables are cleared before setting the new ones, except those matching the
+regexps in WHITE-LIST."
   (match (primitive-fork)
     (0 (launch-environment command profile manifest
-                           #:pure? pure?))
+                           #:pure? pure?
+                           #:white-list white-list))
     (pid (match (waitpid pid)
            ((_ . status) status)))))
 
@@ -672,7 +691,8 @@ message if any test fails."
                                ;; within the container.
                                '("/bin/sh")
                                (list %default-shell))))
-           (mappings   (pick-all opts 'file-system-mapping)))
+           (mappings   (pick-all opts 'file-system-mapping))
+           (white-list (pick-all opts 'inherit-regexp)))
 
       (when container? (assert-container-features))
 
@@ -741,4 +761,5 @@ message if any test fails."
                     (return
                      (exit/status
                       (launch-environment/fork command profile manifest
+                                               #:white-list white-list
                                                #:pure? pure?))))))))))))))
diff --git a/tests/guix-environment.sh b/tests/guix-environment.sh
index 30b21028aa..ccbe027c7b 100644
--- a/tests/guix-environment.sh
+++ b/tests/guix-environment.sh
@@ -1,5 +1,5 @@
 # GNU Guix --- Functional package management for GNU
-# Copyright © 2015, 2016, 2017, 2018 Ludovic Courtès <ludo@gnu.org>
+# Copyright © 2015, 2016, 2017, 2018, 2019 Ludovic Courtès <ludo@gnu.org>
 #
 # This file is part of GNU Guix.
 #
@@ -49,6 +49,19 @@ test -x `sed -r 's/^export PATH="(.*)"/\1/' "$tmpdir/a"`/guile
 
 cmp "$tmpdir/a" "$tmpdir/b"
 
+# Check '--inherit'.
+GUIX_TEST_ABC=1
+GUIX_TEST_DEF=2
+GUIX_TEST_XYZ=3
+export GUIX_TEST_ABC GUIX_TEST_DEF GUIX_TEST_XYZ
+guix environment --bootstrap --ad-hoc guile-bootstrap --pure	\
+     --inherit='^GUIX_TEST_A' --inherit='^GUIX_TEST_D'		\
+     -- "$SHELL" -c set > "$tmpdir/a"
+grep '^PATH=' "$tmpdir/a"
+grep '^GUIX_TEST_ABC=' "$tmpdir/a"
+grep '^GUIX_TEST_DEF=' "$tmpdir/a"
+if grep '^GUIX_TEST_XYZ=' "$tmpdir/a"; then false; else true; fi
+
 # Make sure the exit value is preserved.
 if guix environment --bootstrap --ad-hoc guile-bootstrap --pure \
         -- guile -c '(exit 42)'
-- 
2.20.1

[bug#34486] [PATCH 1/1] environment: Add '--inherit'.

[Thompson, David]

Hi Ludo,

On Fri, Feb 15, 2019 at 6:07 AM Ludovic Courtès <ludo@gnu.org> wrote:
>
> From: Ludovic Courtès <ludovic.courtes@inria.fr>
>
> * guix/scripts/environment.scm (purify-environment): Add 'white-list'
> parameter and honor it.
> (create-environment): Add #:white-list parameter and honor it.
> (launch-environment): Likewise.
> (launch-environment/fork): Likewise.
> (show-help, %options): Add '--inherit'.
> (guix-environment): Define 'white-list' and pass it to
> 'launch-environment/fork'.
> * tests/guix-environment.sh: Test '--inherit'.
> * doc/guix.texi (Invoking guix environment): Document it.

Seems like a good addition to me!

- Dave

[bug#34486] [PATCH 0/1] Add '--inherit' to 'guix environment'

[Ricardo Wurmus]

Hi,

Ludovic Courtès <ludo@gnu.org> writes:

> This new option allows to specify additional variables to be inherited
> in a “pure” (semi-pure?) environment.
>
> The main motivation was the use of the SLURM batch scheduler, which
> defines environment variables that you need to preserve so that things
> like ‘mpirun’ work correctly.

Looks good to me.  The same is needed for Grid Engine.  Previously I
would use “env” with an installed profile for the same effect:

--8<---------------cut here---------------start------------->8---
#!/bin/bash

profile=/path/to/.guix-profile
exec /bin/env - PATH=/opt/uge/bin/lx-amd64 \
                SGE_CELL=default \
                SGE_ARCH=lx-amd64 …
                GUIX_LOCPATH=… \
                /bin/bash --init-file "$profile/etc/profile"
--8<---------------cut here---------------end--------------->8---

I guess the only thing that’s missing now is to activate an installed
environment.

--
Ricardo

bug#34486: [PATCH 0/1] Add '--inherit' to 'guix environment'

[Ludovic Courtès]

Hello,

Ricardo Wurmus <rekado@elephly.net> skribis:

> Ludovic Courtès <ludo@gnu.org> writes:
>
>> This new option allows to specify additional variables to be inherited
>> in a “pure” (semi-pure?) environment.
>>
>> The main motivation was the use of the SLURM batch scheduler, which
>> defines environment variables that you need to preserve so that things
>> like ‘mpirun’ work correctly.
>
> Looks good to me.  The same is needed for Grid Engine.  Previously I
> would use “env” with an installed profile for the same effect:
>
> #!/bin/bash
>
> profile=/path/to/.guix-profile
> exec /bin/env - PATH=/opt/uge/bin/lx-amd64 \
>                 SGE_CELL=default \
>                 SGE_ARCH=lx-amd64 …
>                 GUIX_LOCPATH=… \
>                 /bin/bash --init-file "$profile/etc/profile"

Oh so I guess this is an improvement.  :-)

Pushed as e6e599fa0106f57b9de15f90dcab3795ff1575b6.

> I guess the only thing that’s missing now is to activate an installed
> environment.

Something beyond --search-paths and etc/profile, right?  I’m not sure
what it would look like.

Thanks for your feedback David & Ricardo!

Ludo’.

[bug#34486] [PATCH 0/1] Add '--inherit' to 'guix environment'

[Ricardo Wurmus]

Ludovic Courtès <ludo@gnu.org> writes:

>> I guess the only thing that’s missing now is to activate an installed
>> environment.
>
> Something beyond --search-paths and etc/profile, right?  I’m not sure
> what it would look like.

It doesn’t need to be much.  People can “save” environments with
“--root” but they have no built-in mechanism to “load” an environment
that has been saved like that.

Loading can be done with “env /path/to/bash --init-file
$profile/etc/profile” for activating an environment without mixing its
environment variables into the current environment.  Merging an
environment can be done with “source $profile/etc/profile”.  It would be
nice if there was a simpler, unified interface for this.

    guix environment --load /my/.guix-profile
    guix environment --pure --load /my/.guix-profile
    guix environment --container --load /my/.guix-profile

etc.

--
Ricardo

[bug#34486] [PATCH 0/1] Add '--inherit' to 'guix environment'

[Thompson, David]

On Sat, Feb 16, 2019 at 4:13 AM Ricardo Wurmus <rekado@elephly.net> wrote:
>
>
> Ludovic Courtès <ludo@gnu.org> writes:
>
> >> I guess the only thing that’s missing now is to activate an installed
> >> environment.
> >
> > Something beyond --search-paths and etc/profile, right?  I’m not sure
> > what it would look like.
>
> It doesn’t need to be much.  People can “save” environments with
> “--root” but they have no built-in mechanism to “load” an environment
> that has been saved like that.
>
> Loading can be done with “env /path/to/bash --init-file
> $profile/etc/profile” for activating an environment without mixing its
> environment variables into the current environment.  Merging an
> environment can be done with “source $profile/etc/profile”.  It would be
> nice if there was a simpler, unified interface for this.
>
>     guix environment --load /my/.guix-profile
>     guix environment --pure --load /my/.guix-profile
>     guix environment --container --load /my/.guix-profile

I never got around to implementing this, but I think we should use
some sane defaults to make 'guix environment' save and load
environments without the user having to figure out a bunch of flags.
For example, running 'guix environment' with no flags should
automatically load up the saved profile in the current directory and
instantiate it.  I know about --root, but I never actually use it
because it's kind of a pain.  I'd use persistent environments all the
time if it "just worked".

- Dave

[bug#34486] [PATCH 0/1] Add '--inherit' to 'guix environment'

[Eric Bavier]

[-- Attachment #1: Type: text/plain, Size: 1463 bytes --]

On Fri, 15 Feb 2019 11:42:57 +0100
Ludovic Courtès <ludo@gnu.org> wrote:

> Hello,
> 
> This new option allows to specify additional variables to be inherited
> in a “pure” (semi-pure?) environment.
> 
> The main motivation was the use of the SLURM batch scheduler, which
> defines environment variables that you need to preserve so that things
> like ‘mpirun’ work correctly.
> 
> Thoughts?
> 
> Ludo’.
> 
> Ludovic Courtès (1):
>   environment: Add '--inherit'.
> 
>  doc/guix.texi                | 21 ++++++++++++--
>  guix/scripts/environment.scm | 53 +++++++++++++++++++++++++-----------
>  tests/guix-environment.sh    | 15 +++++++++-
>  3 files changed, 69 insertions(+), 20 deletions(-)
> 

I wonder if the word "inherit" here might be too easily confused with
the idea of package inheritance.  Could we possibly use an option name
that is familiar?  Of-hand I'm thinking of sudo's '-E' and
'--preserve-env'.  SLURM itself uses '--export'.  Both of these tools
requires passing a list of individual environment variables, but
supporting regexp-matching makes sense to me, especially with the SLURM
use-case in mind.

Now I'm having second thoughts.  Since this will be invoked as 'guix
environment --inherit' hopefully the proximity of the word
'environment' will be strong enough to dispell associations with
other types of inheritance.

Anyhow, sending this anyway just to share the concern.

`~Eric

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

[bug#34486] [PATCH 0/1] Add '--inherit' to 'guix environment'

[Ludovic Courtès]

Hi Eric,

Eric Bavier <ericbavier@centurylink.net> skribis:

> I wonder if the word "inherit" here might be too easily confused with
> the idea of package inheritance.  Could we possibly use an option name
> that is familiar?  Of-hand I'm thinking of sudo's '-E' and
> '--preserve-env'.  SLURM itself uses '--export'.  Both of these tools
> requires passing a list of individual environment variables, but
> supporting regexp-matching makes sense to me, especially with the SLURM
> use-case in mind.

That’s a good point, I did wonder too and spent some time thinking about
the choice of words (“inherit”, “preserve”, “keep”, and more elaborate
phrases) and in the end settled with “inherit”.

> Now I'm having second thoughts.  Since this will be invoked as 'guix
> environment --inherit' hopefully the proximity of the word
> 'environment' will be strong enough to dispell associations with
> other types of inheritance.

Yeah, hopefully.

If it sounds confusing or unclear at first, then perhaps we should
change.  What do people think?

Thanks,
Ludo’.

[bug#34486] [PATCH 0/1] Add '--inherit' to 'guix environment'

[Ricardo Wurmus]

Eric Bavier <ericbavier@centurylink.net> writes:
> I wonder if the word "inherit" here might be too easily confused with
> the idea of package inheritance.  Could we possibly use an option name
> that is familiar?  Of-hand I'm thinking of sudo's '-E' and
> '--preserve-env'.  SLURM itself uses '--export'.  Both of these tools
> requires passing a list of individual environment variables, but
> supporting regexp-matching makes sense to me, especially with the SLURM
> use-case in mind.

I think “export” is a worse name, especially in combination with “guix
environment”, which sounds like the Guix environment is to be exported.

“preserve” sounds good to me, but it’s also a character longer than
“inherit” ;)

I’m not a big fan of “inherit” because to me it seems to imply that the
existing environment is to be inherited fully, while the actual intent
is to keep only the selected variables.

“keep” or “allow” sound also good to me.

--
Ricardo

[bug#34486] [PATCH 0/1] Add '--inherit' to 'guix environment'

[Ludovic Courtès]

Hi!

Ricardo Wurmus <rekado@elephly.net> skribis:

> Eric Bavier <ericbavier@centurylink.net> writes:
>> I wonder if the word "inherit" here might be too easily confused with
>> the idea of package inheritance.  Could we possibly use an option name
>> that is familiar?  Of-hand I'm thinking of sudo's '-E' and
>> '--preserve-env'.  SLURM itself uses '--export'.  Both of these tools
>> requires passing a list of individual environment variables, but
>> supporting regexp-matching makes sense to me, especially with the SLURM
>> use-case in mind.
>
> I think “export” is a worse name, especially in combination with “guix
> environment”, which sounds like the Guix environment is to be exported.
>
> “preserve” sounds good to me, but it’s also a character longer than
> “inherit” ;)
>
> I’m not a big fan of “inherit” because to me it seems to imply that the
> existing environment is to be inherited fully, while the actual intent
> is to keep only the selected variables.
>
> “keep” or “allow” sound also good to me.

So, what about adding ‘--preserve’ (or ‘--keep’? I slightly prefer
“preserve”) and keeping ‘--inherit’ as a deprecated alias?

We could perhaps add ‘-E’ as well, reclaiming the long-deprecated
‘--exec’, WDYT?

Ludo’.

[bug#34486] [PATCH 0/1] Add '--inherit' to 'guix environment'

[Ricardo Wurmus]

Ludovic Courtès <ludo@gnu.org> writes:

> Hi!
>
> Ricardo Wurmus <rekado@elephly.net> skribis:
>
>> Eric Bavier <ericbavier@centurylink.net> writes:
>>> I wonder if the word "inherit" here might be too easily confused with
>>> the idea of package inheritance.  Could we possibly use an option name
>>> that is familiar?  Of-hand I'm thinking of sudo's '-E' and
>>> '--preserve-env'.  SLURM itself uses '--export'.  Both of these tools
>>> requires passing a list of individual environment variables, but
>>> supporting regexp-matching makes sense to me, especially with the SLURM
>>> use-case in mind.
>>
>> I think “export” is a worse name, especially in combination with “guix
>> environment”, which sounds like the Guix environment is to be exported.
>>
>> “preserve” sounds good to me, but it’s also a character longer than
>> “inherit” ;)
>>
>> I’m not a big fan of “inherit” because to me it seems to imply that the
>> existing environment is to be inherited fully, while the actual intent
>> is to keep only the selected variables.
>>
>> “keep” or “allow” sound also good to me.
>
> So, what about adding ‘--preserve’ (or ‘--keep’? I slightly prefer
> “preserve”) and keeping ‘--inherit’ as a deprecated alias?

Sounds good to me, though in my opinion “--inherit” hasn’t been around
long enough to warrant deprecation.

> We could perhaps add ‘-E’ as well, reclaiming the long-deprecated
> ‘--exec’, WDYT?

--preserve/-E would be equivalent?

--
Ricardo

[bug#34486] [PATCH 0/1] Add '--inherit' to 'guix environment'

[Ludovic Courtès]

Ricardo Wurmus <rekado@elephly.net> skribis:

> Ludovic Courtès <ludo@gnu.org> writes:
>
>> Hi!
>>
>> Ricardo Wurmus <rekado@elephly.net> skribis:
>>
>>> Eric Bavier <ericbavier@centurylink.net> writes:
>>>> I wonder if the word "inherit" here might be too easily confused with
>>>> the idea of package inheritance.  Could we possibly use an option name
>>>> that is familiar?  Of-hand I'm thinking of sudo's '-E' and
>>>> '--preserve-env'.  SLURM itself uses '--export'.  Both of these tools
>>>> requires passing a list of individual environment variables, but
>>>> supporting regexp-matching makes sense to me, especially with the SLURM
>>>> use-case in mind.
>>>
>>> I think “export” is a worse name, especially in combination with “guix
>>> environment”, which sounds like the Guix environment is to be exported.
>>>
>>> “preserve” sounds good to me, but it’s also a character longer than
>>> “inherit” ;)
>>>
>>> I’m not a big fan of “inherit” because to me it seems to imply that the
>>> existing environment is to be inherited fully, while the actual intent
>>> is to keep only the selected variables.
>>>
>>> “keep” or “allow” sound also good to me.
>>
>> So, what about adding ‘--preserve’ (or ‘--keep’? I slightly prefer
>> “preserve”) and keeping ‘--inherit’ as a deprecated alias?
>
> Sounds good to me, though in my opinion “--inherit” hasn’t been around
> long enough to warrant deprecation.

Well, it’s safer and doesn’t cost much to deprecate it properly.

>> We could perhaps add ‘-E’ as well, reclaiming the long-deprecated
>> ‘--exec’, WDYT?
>
> --preserve/-E would be equivalent?

Yes.

Thanks,
Ludo’.

[bug#34486] [PATCH 0/1] Add '--inherit' to 'guix environment'

[Ricardo Wurmus]

Ludovic Courtès <ludo@gnu.org> writes:

>>> So, what about adding ‘--preserve’ (or ‘--keep’? I slightly prefer
>>> “preserve”) and keeping ‘--inherit’ as a deprecated alias?
>>
>> Sounds good to me, though in my opinion “--inherit” hasn’t been around
>> long enough to warrant deprecation.
>
> Well, it’s safer and doesn’t cost much to deprecate it properly.

True.

>>> We could perhaps add ‘-E’ as well, reclaiming the long-deprecated
>>> ‘--exec’, WDYT?
>>
>> --preserve/-E would be equivalent?
>
> Yes.

Neat.  Let’s do it! :)

-- 
Ricardo

[bug#34486] [PATCH 0/1] Add '--inherit' to 'guix environment'

[Ludovic Courtès]

Ricardo Wurmus <rekado@elephly.net> skribis:

> Ludovic Courtès <ludo@gnu.org> writes:
>
>>>> So, what about adding ‘--preserve’ (or ‘--keep’? I slightly prefer
>>>> “preserve”) and keeping ‘--inherit’ as a deprecated alias?
>>>
>>> Sounds good to me, though in my opinion “--inherit” hasn’t been around
>>> long enough to warrant deprecation.
>>
>> Well, it’s safer and doesn’t cost much to deprecate it properly.
>
> True.
>
>>>> We could perhaps add ‘-E’ as well, reclaiming the long-deprecated
>>>> ‘--exec’, WDYT?
>>>
>>> --preserve/-E would be equivalent?
>>
>> Yes.
>
> Neat.  Let’s do it! :)

Done in dca58219584c1163a9fbf88fccea885eb53bf2af, thanks!

Ludo’.