From: ludo@gnu.org (Ludovic Courtès)
To: Carlo Zancanaro <carlo@zancanaro.id.au>
Cc: Help-Guix@gnu.org
Subject: Re: Package Installation Queries
Date: Thu, 09 Feb 2017 11:00:37 +0100 [thread overview]
Message-ID: <87bmub3cqi.fsf@gnu.org> (raw)
In-Reply-To: <87vaskuzgd.fsf@zancanaro.id.au> (Carlo Zancanaro's message of "Thu, 09 Feb 2017 08:47:46 +1100")
Hello!
Carlo Zancanaro <carlo@zancanaro.id.au> skribis:
> I install all of my Emacs packages via Guix, but in an usual way. I have
> written a script which takes in a list of Emacs packages that I want to
> install, then uses the Elpa importer to generate a Guix package (the
> scheme data structure) which I can build using `guix package -f`. Each
> time I run the script it pulls the most recent version on Melpa, so it's
> not reproducible, but I get the ability to use Guix for roll-backs (and
> in theory I think I could archive my configuration and import it on
> another machine, but I haven't tried that).
It has pros and cons as you write, but I think it’s a neat hack!
I’ve been thinking we should have a way to hook importers and updaters
directly to the command-line interface to facilitate this kind of
experimentation. Say:
guix package --importer=elpa -i something
which would import ‘something’ and its dependencies on the fly.
Ludo’.
next prev parent reply other threads:[~2017-02-09 10:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-08 16:24 Package Installation Queries Niall Dooley
2017-02-08 20:51 ` Alex Kost
2017-02-09 21:36 ` Niall Dooley
2017-02-10 8:55 ` Alex Kost
2017-02-18 16:22 ` Niall Dooley
2017-02-18 20:16 ` Alex Kost
2017-02-10 12:14 ` Leo Famulari
2017-02-08 21:47 ` Carlo Zancanaro
2017-02-09 10:00 ` Ludovic Courtès [this message]
2017-02-19 11:39 ` Ricardo Wurmus
2017-02-09 21:41 ` Niall Dooley
2017-02-19 11:37 ` 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=87bmub3cqi.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=Help-Guix@gnu.org \
--cc=carlo@zancanaro.id.au \
/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.
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).