From: wolf <wolf@wolfsden.cz>
To: Graham Addis <grahamjamesaddis@gmail.com>
Cc: Help-Guix@gnu.org
Subject: Re: guix docker on gitlab-ci
Date: Thu, 1 Jun 2023 23:55:25 +0200 [thread overview]
Message-ID: <ZHkTzXXwvKbTvRha@ws> (raw)
In-Reply-To: <CAA4DTey8EjEWFXjmWJjN1Kqn1KFJzCXcPQekpe4hLX1H_NrNXA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1137 bytes --]
On 2023-05-31 18:47:03 +0100, Graham Addis wrote:
> Hi Wolf,
>
> On Tue, 30 May 2023 at 07:52, Graham Addis <grahamjamesaddis@gmail.com> wrote:
> >
> > ENTRYPOINT ["executable", "param1", "param2"] # The exec form, which
> > is the preferred form:
>
> I realised that pack takes multiple symlink(s) using
>
> --symlink /bin=bin --symlink /opt=opt
>
> I could use the equivalent format for --entry-point
>
> --entry-point executable --entry-point param1 --entry-point param2
>
> This seems the most consistent approach with the current implementation so far.
>
> Thoughts?
>
I think that is a reasonable idea. Only downside is that it would not be
backwards compatible (since currently last --entry-point wins), however I am not
sure if someone actually relies on that behavior.
Backwards compatible way would be keeping --entry-point as it is and introducing
new argument (--entry-point-arg) that could be used to build the argument list,
but I might be overthinking it :).
W.
--
There are only two hard things in Computer Science:
cache invalidation, naming things and off-by-one errors.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-06-01 21:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-24 17:04 guix docker on gitlab-ci Graham Addis
2023-05-29 19:41 ` wolf
2023-05-30 6:52 ` Graham Addis
2023-05-31 17:47 ` Graham Addis
2023-06-01 21:55 ` wolf [this message]
2023-06-02 8:13 ` Graham Addis
2023-06-05 15:37 ` Graham Addis
2023-06-05 17:35 ` wolf
2023-06-05 21:38 ` Graham Addis
2023-06-13 16:56 ` Graham Addis
2023-06-19 15:54 ` Graham Addis
2023-06-01 22:04 ` wolf
2023-06-02 8:06 ` Graham Addis
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=ZHkTzXXwvKbTvRha@ws \
--to=wolf@wolfsden.cz \
--cc=Help-Guix@gnu.org \
--cc=grahamjamesaddis@gmail.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
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.