unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Robby Zambito <contact@robbyzambito.me>
To: "jordila@librebits.info" <jordila@librebits.info>
Cc: help-guix@gnu.org
Subject: Re: Guix home - 'pinning' ?
Date: Mon, 12 Jun 2023 12:16:15 -0400	[thread overview]
Message-ID: <87ttvczlv3.fsf@robbyzambito.me> (raw)
In-Reply-To: <2daa-64864600-75-1eca40e0@207435426>

Hi,

> when using guix-home, is there a way to pin a given package to its 
> current version, so that it stays as it is despite 'guix pull'    
> bringing new commits ?

In your (home-environment (packages ...)) list, you should specify the
package that has the correct version that you want. There are two ways
to do this. You can either create an inferior channel, and specify the
package by looking it up in that channel, or you can apply a
transformation to the package to specify the version.

Using an inferior package will pull the package from a previous version
of Guix - including all of its package inputs. This will pin all of the
transitive dependencies of the package as well. See: info guix Inferiors
for information on how to define an inferior, and how to select a
package from that inferior.

If you want to pin a package to a specific commit, version, branch, etc
of that package, you can use transformations. See: info guix "Defining
Package Variants" for how to use options->transformation, and info guix
"Package Transformation Options" for the available options you can set.

Hope this helps :)

Robby


  reply	other threads:[~2023-06-13 20:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-11 22:08 Guix home - 'pinning' ? jordila
2023-06-12 16:16 ` Robby Zambito [this message]
2023-06-13 15:06   ` Fenix Lopez
2023-06-13 20:02     ` Luis Felipe

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=87ttvczlv3.fsf@robbyzambito.me \
    --to=contact@robbyzambito.me \
    --cc=help-guix@gnu.org \
    --cc=jordila@librebits.info \
    /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).