unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Taylan Kammer <taylan.kammer@gmail.com>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Advantages over Nix?
Date: Mon, 26 Oct 2020 17:14:55 +0100	[thread overview]
Message-ID: <CAJ3okZ3CXr3rv5m_YLdWfzxpxLMOugU6YAR=J=JfrG6qkZQ30g@mail.gmail.com> (raw)
In-Reply-To: <d15d54f9-8ee6-60ad-96c6-d7ab165b4471@gmail.com>

Dear,

On Mon, 26 Oct 2020 at 13:42, Taylan Kammer <taylan.kammer@gmail.com> wrote:
>
> On 26.10.2020 11:41, zimoun wrote:

> I think pack -f docker is going to be the "killer feature" in this case.
>
> Well, the following doesn't seem so complicated either actually:
>
>    https://nix.dev/tutorials/building-and-running-docker-images.html
>
> But I really like how 'guix pack' can generate a tarball just as well,
> which could be deployed and tested anywhere...
>
> I'll need to make a few more comparisons.

Do not miss the '--save-provenance' option. ;-)
It saves the profile/manifest which can be used to rebuild one
manifest.scm file.  You could be interested in [1].  I am running out
of time, but the profile/manifest->manifest.scm converter could be
nice to have. :-)

1:<https://lists.gnu.org/archive/html/guix-devel/2020-09/msg00221.html>


All the best,
simon


  reply	other threads:[~2020-10-26 16:15 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-26  7:42 Advantages over Nix? Taylan Kammer
2020-10-26  9:29 ` Jan Nieuwenhuizen
2020-10-26 11:36   ` Taylan Kammer
2020-10-26 23:39     ` Ludovic Courtès
2020-10-27 10:35       ` Pjotr Prins
2020-10-27 13:14         ` zimoun
2020-10-28  5:58           ` Pjotr Prins
2020-10-26 10:41 ` zimoun
2020-10-26 11:44   ` Pierre Neidhardt
2020-10-26 12:46     ` Taylan Kammer
2020-10-26 12:42   ` Taylan Kammer
2020-10-26 16:14     ` zimoun [this message]
2020-10-26 20:29       ` Yasuaki Kudo
2020-10-26 22:32 ` Ricardo Wurmus

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='CAJ3okZ3CXr3rv5m_YLdWfzxpxLMOugU6YAR=J=JfrG6qkZQ30g@mail.gmail.com' \
    --to=zimon.toutoune@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=taylan.kammer@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 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).