all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Carlo Zancanaro <carlo@zancanaro.id.au>
To: Fredrik Salomonsson <plattfot@posteo.net>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Best practice when dealing with a broken package for guix home?
Date: Mon, 15 Jan 2024 15:55:47 +1100	[thread overview]
Message-ID: <87o7dni4a4.fsf@zancanaro.id.au> (raw)
In-Reply-To: <87h6jfzf14.fsf@posteo.net> (Fredrik Salomonsson's message of "Sun, 14 Jan 2024 23:11:35 +0000")

On Sun, Jan 14 2024, Fredrik Salomonsson wrote:
> 3) Copy an older definition that works to my custom channel, add a
> prefix and use that until it is fixed.

This is what I do. Or, more accurately, I copy it into my home.scm file
and use the package object directly. That way it's clear why it exists,
and it's easier to remove when I no longer need it.

> My question what is the best practice for this? ... Maybe something
> with the time-machine?

I don't know about best practice, but I think at one point I did use
inferiors for this (which is what time machine users under the hood).
Unfortunately I can't remember why I stopped.

If you'd like to go this way, the documentation in "(guix) Inferiors"
has a short example of getting a package out of a different Guix
version. It's pretty straightforward.

Carlo


  parent reply	other threads:[~2024-01-15  4:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-14 23:11 Best practice when dealing with a broken package for guix home? Fredrik Salomonsson
2024-01-15  1:21 ` Felix Lechner via
2024-01-16 17:50   ` Fredrik Salomonsson
2024-01-17  2:41     ` Felix Lechner via
2024-01-18 11:28       ` Simon Tournier
2024-01-18 17:59         ` Fredrik Salomonsson
2024-01-18 19:18           ` Tomas Volf
2024-01-18 21:54             ` Felix Lechner via
2024-01-15  4:55 ` Carlo Zancanaro [this message]
2024-01-16 17:53   ` Fredrik Salomonsson

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=87o7dni4a4.fsf@zancanaro.id.au \
    --to=carlo@zancanaro.id.au \
    --cc=help-guix@gnu.org \
    --cc=plattfot@posteo.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.
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.