From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: Olivier Dion <olivier.dion@polymtl.ca>, guix-devel@gnu.org
Subject: Re: Package's inputs for developer?
Date: Tue, 08 Mar 2022 21:24:02 +0100 [thread overview]
Message-ID: <1fb349d0e9eeae9be10345fbe9002daa9ace8ed5.camel@gmail.com> (raw)
In-Reply-To: <87ee3fvys1.fsf@laura>
Hi Olivier,
Am Sonntag, dem 06.03.2022 um 11:19 -0500 schrieb Olivier Dion via
Development of GNU Guix and the GNU System distribution.:
> Hi Guix,
>
> I often find my self using inheritance of package to add native-inputs
> that are not stricly necessary for building the project, but are used
> for developement purpose like so:
> -------------------------------------------------
> (define base-native-inputs (list ...))
>
> (define my-package
> (package
> ...
> (native-inputs base-native-inputs)
> ...))
>
> ;; Developers version
> (package
> (inherit my-package)
> (native-inputs
> (append base-native-inputs
> (list gdb lcov))))
> -------------------------------------------------
>
> I guess this is the correct way of doing it or perhaps I should put gdb
> and lcov in the base-native-inputs?. But I was thinking that perhaps
> something like `(developer-inputs (list gdb lcov))` would be better,
> since these inputs are not stricly necessary for building the
> package.
Note, that manifests exist and you should use them. An example (from
[1]):
--8<---------------cut here---------------start------------->8---
(use-modules [...])
(define %here (dirname (current-filename)))
(packages->manifest
(cons*
emacs emacs-geiser
guile-hall
(filter-map
(match-lambda
((_ (? package? package) output) (list package output))
((_ (? package? package)) package)
(else #f))
(package-development-inputs
(load (string-append %here "/guix.scm"))))))
--8<---------------cut here---------------end--------------->8---
This adds emacs, emacs-geiser and guile-hall to the package-
development-inputs of the package described in "./guix.scm" and
constructs an environment with all of them.
Cheers
[1] https://gitlab.com/spritely/guile-goblins/
prev parent reply other threads:[~2022-03-08 20:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-06 16:19 Package's inputs for developer? Olivier Dion via Development of GNU Guix and the GNU System distribution.
2022-03-07 17:17 ` Kaelyn
2022-03-07 18:31 ` Olivier Dion via Development of GNU Guix and the GNU System distribution.
2022-03-08 16:00 ` zimoun
2022-03-08 16:45 ` Olivier Dion via Development of GNU Guix and the GNU System distribution.
2022-03-08 18:44 ` zimoun
2022-03-08 17:06 ` Danny Milosavljevic
2022-03-08 20:24 ` Liliana Marie Prikler [this message]
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=1fb349d0e9eeae9be10345fbe9002daa9ace8ed5.camel@gmail.com \
--to=liliana.prikler@gmail.com \
--cc=guix-devel@gnu.org \
--cc=olivier.dion@polymtl.ca \
/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).