From: Andy Tai <atai@atai.org>
To: help-guix@gnu.org
Subject: question on setting up guix.scm for project development
Date: Sun, 13 Nov 2022 22:29:15 -0800 [thread overview]
Message-ID: <CAJsg1E8Ay1v7=XYSQhCHDPZq5Ra9XpLbzf0G7o44d6Eh7m8Eiw@mail.gmail.com> (raw)
Hi, guix allows setting up an environment containing all the
dependencies for development of a package; this can be done via a
guix.scm file containing the package definition.
My question is, if I am developing a package which has dependencies
with newer versions than what is available in the guix repo, how can I
use the guix.scm file to bring in the new version of the dependencies?
As an example:
Say my package "my-package" has dependencies d1, d2, d3
where d2 in the current guix package repo is at version 0.1.2 but I
need a later release version 0.1.4; so I tried something like this:
----guix.scm---
(use-modules (guix packages)
....)
(define-public d2-0.1.4
(package
(name "d2")
(version "0.1.4")
...
)
(define-public my-package
(package
(name "my-package")
(version "0.1")
...
(input (list d1 d2-0.1.4 d3...)
....
))
my-package
---end guix.scm--
and if I use
guix shell -f -d ./guix.scm
this does not seem to generate an environment that contains the new
dependency, that is d2 version 0.1.4
I wonder how can this made to work? Ideally no need to create a
private channel or such.. Thanks for info on this.
next reply other threads:[~2022-11-15 1:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-14 6:29 Andy Tai [this message]
2022-11-18 16:53 ` question on setting up guix.scm for project development Ludovic Courtès
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='CAJsg1E8Ay1v7=XYSQhCHDPZq5Ra9XpLbzf0G7o44d6Eh7m8Eiw@mail.gmail.com' \
--to=atai@atai.org \
--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.
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).