[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: ‘guix pack’ & entry point
From: |
Ludovic Courtès |
Subject: |
Re: ‘guix pack’ & entry point |
Date: |
Fri, 29 Sep 2017 13:58:42 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/25.3 (gnu/linux) |
Ricardo Wurmus <address@hidden> skribis:
> Ludovic Courtès <address@hidden> writes:
>
>> Bonus: what would the tarball backend do with the entry point? Ignore it?
>
> It should end up as a script in the tarball IMO.
With an easily recognizable fixed name? Like /init or /run?
> Maybe we want a more general feature here. For example, we had the
> problem that /etc/environment is not actually sourced by default. Maybe
> what we need is a way to start services that are then configured like
> any other shepherd service…? Or is this too much?
I think it could be useful, but it’s a special case of the more general
notion of an “entry point”: a possible entry point could be ‘shepherd’,
but it doesn’t have to.
Ludo’.