all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Marek Paśnikowski" <marekpasnikowski@protonmail.com>
To: "Przemysław Kamiński" <cgenie@pm.me>
Cc: help-guix@gnu.org
Subject: Re: streamlining custom package development
Date: Fri, 03 Mar 2023 11:05:03 +0000	[thread overview]
Message-ID: <KNEo9veTFs7uqCG8bcxV92iKVIVyuKUX3tjSEISt26heXV_LwxJ52VeqtpTnHr8Gsgl_-e0iMknoEEqhtlggKmeB_TDVwfHpKRhsVq1ebpw=@protonmail.com> (raw)
In-Reply-To: <d6778040-23d7-f5d1-89a3-0d8b5ccf211f@pm.me>

> This is tedious. Is there a way to automate this a bit more?

Only slightly.  Do remember, that Guix is purely functional.  Your pain is with the chain of dependencies.

I recently went through a similar ordeal while packaging an update to Nix.  I suggest to:
1. look up the dependency list on the program's or library's documentation;
2. add the dependencies to the input lists;
3. attempt to build the target package and write the package definitions for the missing dependecies;
4. keep iterating the above until completion.

It should help you to think of this iteration as a Test Driven Development process.  The guix build  is your test suite, which you want to get green.

I also recommend to use the -v3 option - it will allow you to see the log immediately.

Best Regards,
Marek Pasnikowski


  reply	other threads:[~2023-03-03 13:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-03 10:44 streamlining custom package development Przemysław Kamiński
2023-03-03 11:05 ` Marek Paśnikowski [this message]
2023-03-07 13:31 ` Simon Tournier
2023-03-07 16:02 ` Ludovic Courtès
2023-03-07 16:57   ` Przemysław Kamiński
2023-03-07 18:28     ` Simon Tournier

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='KNEo9veTFs7uqCG8bcxV92iKVIVyuKUX3tjSEISt26heXV_LwxJ52VeqtpTnHr8Gsgl_-e0iMknoEEqhtlggKmeB_TDVwfHpKRhsVq1ebpw=@protonmail.com' \
    --to=marekpasnikowski@protonmail.com \
    --cc=cgenie@pm.me \
    --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.
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.