From: "Ludovic Courtès" <ludo@gnu.org>
To: Pjotr Prins <pjotr.public12@thebird.nl>
Cc: guix-devel@gnu.org
Subject: Re: Guix containers 'advertised' in git repos
Date: Fri, 28 Aug 2020 12:33:04 +0200 [thread overview]
Message-ID: <87imd3qcv3.fsf@gnu.org> (raw)
In-Reply-To: <20200810103658.swmptuhdfv4w2why@thebird.nl> (Pjotr Prins's message of "Mon, 10 Aug 2020 12:36:58 +0200")
Hello,
Pjotr Prins <pjotr.public12@thebird.nl> skribis:
> We are using Guix containers for deployment and software development.
> I was thinking it would be nice to advertise them in the git repos.
>
> Maybe we can standardise on that. What I have now is have a file
>
> .git-deploy
>
> for deployment. E.g.,
> https://github.com/encryption4genetics/HEGP-website/blob/master/.guix-deploy
>
> and
>
> .git-dev
>
> for development. E.g.,
> https://github.com/genetics-statistics/GEMMA/blob/master/.guix-dev
[...]
David Dashyan <mail@davie.li> skribis:
> We do the same thing, kind of, but due to our CLA restrictions we have
> everything in separate repository.
>
> https://github.com/ipdb/bigchaindb-guix
>
> I've named the file "activate" which is python's idiom taken from
There’s a rather widespread convention for ‘guix.scm’, to be passed to
‘guix environment -l’ or ‘guix package -f’.
However, there’s currently no tool to declare the container parameters,
which is why your ‘.guix-deploy’ file above is essentially a shell
script.
A long time ago Dave Thompson suggested having an <environment> (or
similar) data type on top of <manifest>, which would describe that sort
of thing. Perhaps something to keep in mind for ‘guix shell’?
Ludo’.
prev parent reply other threads:[~2020-08-28 10:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-10 10:36 Guix containers 'advertised' in git repos Pjotr Prins
2020-08-10 14:53 ` David Dashyan
2020-08-27 10:53 ` zimoun
2020-08-28 10:33 ` Ludovic Courtès [this message]
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87imd3qcv3.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=pjotr.public12@thebird.nl \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).