From: zimoun <zimon.toutoune@gmail.com>
To: Emmanuel Medernach <emmanuel.medernach@gmail.com>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Help on writing package definitions
Date: Thu, 23 Apr 2020 16:17:36 +0200 [thread overview]
Message-ID: <CAJ3okZ2kzwFXWiMEVaoDL+DOzpTUbHRdrRYrto-uoLkb7pnnrA@mail.gmail.com> (raw)
In-Reply-To: <CAC_pKx8S5zBp7iTAuLjFRxqjMyee62ymgkvWaBbPS74oD1Lb8g@mail.gmail.com>
On Thu, 23 Apr 2020 at 14:21, Emmanuel Medernach
<emmanuel.medernach@gmail.com> wrote:
> Yes, it is not listed in this list because it is specific to the project. I would like to be able to create one new license but the license function is not exported.
It appears to me a good idea to export the record 'license'.
The tiniest trivial patch [1] ;-)
[1] http://issues.guix.gnu.org/40795
> How do you debugged this issue to find that we have to add pkgconfig ?
Because the 'modify-phases' uses pkg-config and everything is isolated.
To be fully clean, 'pkg-config' should go to 'native-inputs' [2];
maybe the others too, do not know enough about your package.
[2] https://guix.gnu.org/manual/en/guix.html#package-Reference
All the best,
simon
next prev parent reply other threads:[~2020-04-23 14:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-23 6:32 Help on writing package definitions Emmanuel Medernach
2020-04-23 10:00 ` zimoun
2020-04-23 12:21 ` Emmanuel Medernach
2020-04-23 14:17 ` zimoun [this message]
2020-04-23 16:44 ` Leo Famulari
2020-04-23 17:11 ` zimoun
-- strict thread matches above, loose matches on Subject: below --
2020-04-23 9:41 Vincent Legoll
2020-04-23 12:09 ` Emmanuel Medernach
2020-04-23 12:17 ` Vincent Legoll
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=CAJ3okZ2kzwFXWiMEVaoDL+DOzpTUbHRdrRYrto-uoLkb7pnnrA@mail.gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=emmanuel.medernach@gmail.com \
--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).