From: Andy Tai <atai@atai.org>
To: Julien Lepiller <julien@lepiller.eu>
Cc: guix-devel@gnu.org
Subject: Re: Fwd: question on setting up guix.scm for project development
Date: Tue, 15 Nov 2022 07:40:05 -0800 [thread overview]
Message-ID: <CAJsg1E_P1L8eFqrTQKpng8ZBc-EZjRdP0jrsR2-r3MTG1Nzgog@mail.gmail.com> (raw)
In-Reply-To: <331E65BE-81A7-4484-9B10-DC2021979D25@lepiller.eu>
[-- Attachment #1: Type: text/plain, Size: 1119 bytes --]
Hi, thanks.
guix shell -D -f guix.scm
did work for me.... I did not see d2 0.1.4 from
guix package --list-installed
or
guix package --list-available
but
pkg-config --modversion d2
did show 0.1.4 So it is there, in this guix shell.
Thanks for all the replies to this question.
On Mon, Nov 14, 2022 at 10:15 PM Julien Lepiller <julien@lepiller.eu> wrote:
> I think you got it right, I've used thas in the past. Maybe your cli
> options are out of order? Instead of -f -d, try -D -f. Do you even have d1
> or d3 in your current shell? Could they come from outside?
>
> Le 14 novembre 2022 19:41:58 GMT+01:00, Andy Tai <atai@atai.org> a écrit :
>>
>>
>> ----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---
>>
>>
[-- Attachment #2: Type: text/html, Size: 3135 bytes --]
next prev parent reply other threads:[~2022-11-15 15:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAJsg1E8Ay1v7=XYSQhCHDPZq5Ra9XpLbzf0G7o44d6Eh7m8Eiw@mail.gmail.com>
2022-11-14 18:41 ` Fwd: question on setting up guix.scm for project development Andy Tai
2022-11-15 2:02 ` Pjotr Prins
2022-11-15 6:15 ` Julien Lepiller
2022-11-15 15:40 ` Andy Tai [this message]
2022-11-15 16:46 ` Julien Lepiller
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=CAJsg1E_P1L8eFqrTQKpng8ZBc-EZjRdP0jrsR2-r3MTG1Nzgog@mail.gmail.com \
--to=atai@atai.org \
--cc=guix-devel@gnu.org \
--cc=julien@lepiller.eu \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).