From: Pierre Neidhardt <mail@ambrevar.xyz>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Guix pull chokes on uglify-js
Date: Thu, 05 Dec 2019 16:03:07 +0100 [thread overview]
Message-ID: <87immubys4.fsf@ambrevar.xyz> (raw)
In-Reply-To: <87tv6eg6tg.fsf@nckx>
[-- Attachment #1: Type: text/plain, Size: 876 bytes --]
Tobias Geerinckx-Rice <me@tobias.gr> writes:
> Pierre Neidhardt 写道:
>> Let me know if there is anything else that bot broken in the
>> process.
>
> Adding your local repository to ~/.guix/config/channels.scm and
> running ‘guix pull’ after committing (and before pushing) should
> reproduce the downstream experience quite accurately, although I
> haven't tried it myself.
Yes, it also works with `guix pull --url=...`, but I would like to avoid
touch my user guix checkout profile.
Maybe this would be a viable alternative then:
--8<---------------cut here---------------start------------->8---
guix pull --url=... && guix package -p ~/.config/guix/current --roll-back
--8<---------------cut here---------------end--------------->8---
Not atomic, but good enough I suppose.
Thoughts?
--
Pierre Neidhardt
https://ambrevar.xyz/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2019-12-05 15:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-28 19:58 Guix pull chokes on uglify-js Tobias Geerinckx-Rice
2019-11-28 20:47 ` Pierre Neidhardt
2019-11-29 14:42 ` Pierre Neidhardt
2019-11-29 15:25 ` zimoun
2019-12-02 9:35 ` Pierre Neidhardt
2019-12-05 12:50 ` Pierre Neidhardt
2019-12-05 14:46 ` Tobias Geerinckx-Rice
2019-12-05 14:54 ` Pierre Neidhardt
2019-12-05 14:55 ` Tobias Geerinckx-Rice
2019-12-05 15:03 ` Pierre Neidhardt [this message]
2019-12-05 15:12 ` Marius Bakke
2019-12-05 15:19 ` Pierre Neidhardt
2019-12-05 15:37 ` Pierre Neidhardt
2019-12-05 16:06 ` Tobias Geerinckx-Rice
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=87immubys4.fsf@ambrevar.xyz \
--to=mail@ambrevar.xyz \
--cc=guix-devel@gnu.org \
--cc=me@tobias.gr \
/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.