unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: <cdelia@dc.uba.ar>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: help-guix@gnu.org
Subject: Re: rolling back only a single package
Date: Mon, 31 Dec 2018 04:11:27 -0300	[thread overview]
Message-ID: <87wonq1880.fsf@dc.uba.ar> (raw)
In-Reply-To: <87efa14sgu.fsf@elephly.net> (Ricardo Wurmus's message of "Fri, 28 Dec 2018 15:49:05 +0100")


Hi Ricardo,

thanks for answering,

so basically this is equivalent to find the generation of commit
65956a... and invoking guix-generation-x to install guile-json.

Yes, I see why this it's better than using "guix package -i *" and it
relates well to my other question about profile -> packages definitions
generation.

Just write manifests, instantiate them and when it's time to migrate the
pacakges definitions will already there.

What happens if you then do "guix package -i guile-json" or if somewhere
in the future "guix package -U" after a pull?

It will honor the manifest or just install the guile-json on the package
definition?

I don't know if I can make my mind on what sort of behaviur should be
best but maybe I'm more towards the idea that a manifest should take
precedence, maybe with an override flag.

Anyway I can try and check later what guix does.

Thanks! and have a happy new year eve.

Ricardo Wurmus <rekado@elephly.net> writes:
> Inferiors work, but you’d use them in manifests.  The idea is to install
> the package with an old version of Guix, but to do it in code instead of
> manually.  Here’s an example:
>
> (use-modules (guix inferior) (guix channels)
>              (srfi srfi-1))   ;for 'first'
>
> (define channels
>   ;; This is the old revision from which we want to
>   ;; extract guile-json.
>   (list (channel
>          (name 'guix)
>          (url "https://git.savannah.gnu.org/git/guix.git")
>          (commit
>           "65956ad3526ba09e1f7a40722c96c6ef7c0936fe"))))
>
> (define inferior
>   ;; An inferior representing the above revision.
>   (inferior-for-channels channels))
>
> ;; Now create a manifest with the current "guile" package
> ;; and the old "guile-json" package.
> (packages->manifest
>  (list (first (lookup-inferior-packages inferior "guile-json"))
>        (specification->package "guile")))
>
> You can instantiate the manifest the usual way:
>
>     guix package -m /path/to/manifest.scm
>
> --
> Ricardo

--
Catriel

  reply	other threads:[~2018-12-31  7:12 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-27 19:52 rolling back only a single package cdelia
2018-12-28  7:55 ` Pierre Neidhardt
     [not found]   ` <7bbd5b5a38121bf9a70c1fbe095c39b8@dc.uba.ar>
2018-12-28 22:19     ` cdelia
2018-12-28 11:35 ` Tonton
2018-12-30 22:57   ` cdelia
2018-12-31 15:17     ` Tonton
2018-12-28 13:34 ` Björn Höfling
2018-12-28 14:49   ` Ricardo Wurmus
2018-12-31  7:11     ` cdelia [this message]
2018-12-31  8:23       ` Ricardo Wurmus
2018-12-30 23:37   ` cdelia
2018-12-31  0:59   ` cdelia
     [not found] ` <45406B3B-5E5F-4444-9679-A5DB43D9AE50@pretty.Easy.privacy>
2018-12-28 22:15   ` cdelia
2018-12-29 18:35     ` swedebugia
2018-12-30 22:40       ` Catriel Omar D'Elía

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=87wonq1880.fsf@dc.uba.ar \
    --to=cdelia@dc.uba.ar \
    --cc=help-guix@gnu.org \
    --cc=rekado@elephly.net \
    /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).