all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Simon Tournier <zimon.toutoune@gmail.com>
To: Rodrigo Morales <moralesrodrigo1100@gmail.com>, help-guix@gnu.org
Subject: Re: Newbie: How to debug my custom packages? Is there something like Emacs' edebug but for Guix packages?
Date: Fri, 07 Apr 2023 10:33:46 +0200	[thread overview]
Message-ID: <87y1n4ks5x.fsf@gmail.com> (raw)
In-Reply-To: <CAGxMbPaXDZu8StdSDhE78W5kpU6UQbqXvEUr8zS9LeL2MeRDBA@mail.gmail.com>

Hi,

On ven., 07 avril 2023 at 04:20, Rodrigo Morales <moralesrodrigo1100@gmail.com> wrote:

>   |    (build-system trivial-build-system)

Please note that the ’trivial-build-system’ is the less trivial build
system.  I think you need ’copy-build-system’ instead.

Roughly speaking, using this,

    mkdir path/to/test/folder
    edit path/to/test/folder/rime.scm

where rime.scm contains the block you provided.  Then my trial-error
loop looks like: 

    guix build -L path/to/test/folder rime-wubi-8105 -K

With the option ’-K’, it keeps the temporary build under
/tmp/guix-<something> but here it does not seem very useful.

Last, you can check with,

--8<---------------cut here---------------start------------->8---
$ tree $(guix build -L /tmp/foo rime-wubi-8105 --no-grafts)
/gnu/store/nqc3sfndq6665d0lfrb3h6j58d559j6a-rime-wubi-8105-1.0
└── share
    └── rime-data
        ├── wubi86_8105.dict.yaml
        └── wubi86_8105.schema.yaml
--8<---------------cut here---------------end--------------->8---


Hope that helps,
simon


      reply	other threads:[~2023-04-07 10:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-07  4:20 Newbie: How to debug my custom packages? Is there something like Emacs' edebug but for Guix packages? Rodrigo Morales
2023-04-07  8:33 ` Simon Tournier [this message]

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=87y1n4ks5x.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --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.