all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Hilton Chain <hako@ultrarare.space>
To: Rodrigo Morales <moralesrodrigo1100@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: Newbie: How to edit a faulty package definition?
Date: Sun, 25 Jun 2023 12:57:59 +0800	[thread overview]
Message-ID: <87leg8kujs.wl-hako@ultrarare.space> (raw)
In-Reply-To: <CAGxMbPZ7v3utzq4-jNcXAXi-Om3Y-UKsqLvZSUmOmF7Ej5LOYA@mail.gmail.com>

Hi Rodrigo,

On Sun, 25 Jun 2023 11:30:42 +0800,
Rodrigo Morales wrote:
...
>   | (define-module (my test-2)
...
>   | (define-public emacs-subed
>   |   (package
>   |     (name "emacs-subed")
...
>   The main topic of this thread could have been: How to make "guix home"
>   give higher priority to a path specified through the `-L' flag? But I
>   decided not to ask for help on `guix home', because there are less
>   "guix home" users than Guix users, so I might need to wait
>   significantly more to get some help. I'd rather learn how to edit
>   package definitions and make `guix package -i' aware of that. I've
>   opened another thread on a question related to "guix edit" [here].

I have a solution but not about priorities.

The solution depends on how you add packages to your home environment.

If you are referencing them as variables, you can change the variable name of
your package, or directly referencing it with (@ (my test-2) emacs-subed).

If you are using the specification->package procedure, you can change the name
field of your package definition.


  reply	other threads:[~2023-06-25  8:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-25  3:30 Newbie: How to edit a faulty package definition? Rodrigo Morales
2023-06-25  4:57 ` Hilton Chain [this message]
2023-06-26 22:21 ` Skyler Ferris

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=87leg8kujs.wl-hako@ultrarare.space \
    --to=hako@ultrarare.space \
    --cc=help-guix@gnu.org \
    --cc=moralesrodrigo1100@gmail.com \
    /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.