From: zimoun <zimon.toutoune@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>,
Philippe SWARTVAGHER <philippe.swartvagher@inria.fr>
Cc: help-guix@gnu.org
Subject: Re: Package variant defined in manifest not visible by Guix
Date: Tue, 17 Aug 2021 09:17:09 +0200 [thread overview]
Message-ID: <86czqcpmkq.fsf@gmail.com> (raw)
In-Reply-To: <87eeath300.fsf@elephly.net>
Hi Philippe,
On Mon, 16 Aug 2021 at 16:34, Ricardo Wurmus <rekado@elephly.net> wrote:
> 3) Create a module and use it however you want.
[...]
> Put this in a file “my/packages/storm.scm” and then set the
> GUIX_PACKAGE_PATH environment variable to the directory containing
> “my” (e.g. $HOME/code/guix/custom containing
> $HOME/code/guix/custom/my/packages/storm.scm).
Do not miss the CLI option ’--load-path’. Instead of setting the
environment variable GUIX_PACKAGE_PATH, you can also do:
guix build --load-path=my/packages/storm.scm <your-variant-package-name>
> Note that you haven’t overridden the “name” field of the original
> “starpu” package, so on the command line the package cannot be
> distinguished (unless you use “-e '(@ (my packages storm)
> starpu-maxnodes1)'”). Do this to also change the name on the
> command line:
>
> --8<---------------cut here---------------start------------->8---
> (define starpu-maxnodes1
> (package
> (inherit starpu)
> (name "starpu-maxnodes1")
> (arguments
> (substitute-keyword-arguments (package-arguments starpu)
> ((#:configure-flags flags '())
> `(cons "--enable-maxnodes=1"
> ,flags))))))
> --8<---------------cut here---------------end--------------->8---
In the initial error message, the package is unknown because the package
name ’starpu-maxnodes1’ does not exist, it is the name of the symbol.
And the symbol ’starpu-maxnodes1’ has the name ’starpu’. Does it make
sense?
Cheers,
simon
next prev parent reply other threads:[~2021-08-17 7:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-16 8:08 Package variant defined in manifest not visible by Guix Philippe SWARTVAGHER
2021-08-16 12:04 ` Efraim Flashner
2021-08-16 14:34 ` Ricardo Wurmus
2021-08-17 7:17 ` zimoun [this message]
2021-08-18 8:57 ` Philippe SWARTVAGHER
2021-08-18 13:21 ` zimoun
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86czqcpmkq.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=help-guix@gnu.org \
--cc=philippe.swartvagher@inria.fr \
--cc=rekado@elephly.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).