From: Fenix Lopez <jordila@librebits.info>
To: help-guix@gnu.org
Subject: Re: Guix home - 'pinning' ?
Date: Tue, 13 Jun 2023 17:06:54 +0200 [thread overview]
Message-ID: <f90aa32f-5e79-bc58-d5de-d70154a5d30e@librebits.info> (raw)
In-Reply-To: <87ttvczlv3.fsf@robbyzambito.me>
Hi !
Thanks for the clarifiction, Robby.
In order to give some more context , may i add the fact that the package
in question
is not being compiled/derived when entering the build phase ? In
consquence, the whole 'guix home reconfigure' gets stopped...
That's the underlaying reason why i was wondering how to pin that
'offending' package.
Umh... leaving package version 'pinning' aside, umh... Is there
another way to prevent such described scenario ? how to get ' guix home
reconfigure'
finish the whole process regardless the issue described ?
thanks, thanks , thnaks for your attention
F
On 12/6/23 18:16, Robby Zambito wrote:
> 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
next prev parent reply other threads:[~2023-06-13 15:08 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
2023-06-13 15:06 ` Fenix Lopez [this message]
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=f90aa32f-5e79-bc58-d5de-d70154a5d30e@librebits.info \
--to=jordila@librebits.info \
--cc=help-guix@gnu.org \
/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).