all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ison <ison@airmail.cc>
To: 白い熊 <help-guix_gnu.org@sumou.com>
Cc: help-guix@gnu.org
Subject: Re: Building and installing packages with modifications
Date: Sun, 24 Feb 2019 11:46:20 -0700	[thread overview]
Message-ID: <20190224184620.w2xqvaw5byjk7bnb@cf0> (raw)
In-Reply-To: <B4DF75A4-AF17-4082-AF29-36489B4719A4@sumou.com>

Since this hasn't received any replies I'll give my solution, although I
apologize in advance if this isn't the "best" way to do it.

When I want to modify a package that I install via "guix package -i" (as opposed
to using the GuixSD system configuration) I just create a new file for each such
package that inherits the default package and then override any options I need.
For example, in the case of curl you could make a file with the contents:
--------------------
(use-modules ((guix licences) #:prefix license:)
              (gnu packages)
              (gnu packages curl)
              (guix packages)
              (guix utils)))

(package
  (inherit curl)
  (substitute-keyword-arguments (package-arguments curl)
    ((#:tests? #f #f)
      #f)))
--------------------
which will just inherit curl and only modify the flag "tests?" to disable tests.
Everything else will be kept the same. Then if you save that to a file called
my-curl.scm you could install it to your guix profile with
"guix package -f my-curl.scm"

  reply	other threads:[~2019-02-24 18:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-16 15:12 Building and installing packages with modifications 白い熊
2019-02-24 18:46 ` ison [this message]
2019-02-24 19:06   ` 白い熊@相撲道
2019-02-24 23:17     ` ison
2019-02-26  9:34       ` Chris Marusich
2019-02-24 19:30   ` Wayne
2019-02-26  9:26   ` Chris Marusich
2019-03-12  3:37     ` Wayne
2019-02-24 20:01 ` Gábor Boskovits

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=20190224184620.w2xqvaw5byjk7bnb@cf0 \
    --to=ison@airmail.cc \
    --cc=help-guix@gnu.org \
    --cc=help-guix_gnu.org@sumou.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.