From: Hartmut Goebel <h.goebel@crazy-compilers.com>
To: 54820@debbugs.gnu.org
Subject: bug#54820: build-systems: inconsistent use of standard-packages
Date: Sat, 9 Apr 2022 18:24:55 +0200 [thread overview]
Message-ID: <73a4b99c-23db-ac72-2a09-1c454dc1b3e5@crazy-compilers.com> (raw)
Build-systems are adding „@(standard-packages)“ inconsistently to
„host-packages“ or „build-packages”. For one developing a new
build-system it is not clear which is the correct form.
Some (e.g. texlive, ruby, python) add it to „host-inputs“)
(host-inputs `(,@(if source
`(("source" ,source))
'())
,@inputs
;; Keep the standard inputs of 'gnu-build-system'.
,@(standard-packages)))
Some add it to „build-inputs (e.g. gnu, cmake, qt):
(build-inputs `(,@(if source
`(("source" ,source))
'())
,@`(("cmake" ,cmake))
,@native-inputs
,@(if target
;; Use the standard cross inputs of
;; 'gnu-build-system'.
(standard-cross-packages target 'host)
'())
;; Keep the standard inputs of 'gnu-build-system'.
,@(standard-packages)))
Expected:
Either
a) review and align the code of all build-systems, or
b) add a comment to every build-system briefly explaining why in host
resp. build-packages here,
c) document how and why to use which form.
Since as far as I've seen there is no detailed „How to write a
build-system“, developers (well, me :-) tend to develop new
build-systems based on existing ones. Thus (a) or (b) seem the easier
and quicker solution.
Reproduce:
grep -A5 -B5 standard-packages guix/build-system/*.scm
--
Regards
Hartmut Goebel
| Hartmut Goebel | h.goebel@crazy-compilers.com |
| www.crazy-compilers.com | compilers which you thought are impossible |
next reply other threads:[~2022-04-09 16:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-09 16:24 Hartmut Goebel [this message]
2022-04-09 17:52 ` bug#54820: build-systems: inconsistent use of standard-packages Maxime Devos
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=73a4b99c-23db-ac72-2a09-1c454dc1b3e5@crazy-compilers.com \
--to=h.goebel@crazy-compilers.com \
--cc=54820@debbugs.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.
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).