From: Maxime Devos <maximedevos@telenet.be>
To: Julien Lepiller <julien@lepiller.eu>, guix-devel@gnu.org
Subject: Re: Reducing useless module imports
Date: Sat, 4 Feb 2023 15:12:22 +0100 [thread overview]
Message-ID: <997ca8a8-ac79-de44-fb84-958f514c75c9@telenet.be> (raw)
In-Reply-To: <20230203181126.5ee4003c@tachikoma.lepiller.eu>
[-- Attachment #1.1.1: Type: text/plain, Size: 833 bytes --]
On 03-02-2023 18:11, Julien Lepiller wrote:
> gnu packages minetest) imports (guix build-system
> minetest) but never uses the minetest-build-system. (gnu packages
> abiword) uses (guix build-system gnu) but does not use the
> gnu-build-system.
>
The build-system minetest-build-system does not exist; it's
minetest-mod-build-system, which happens to be defined in (guix
build-system build-system). As such, (gnu packages minetest) actually
does use (guix build-system minetest).
The idea was that in the future we might also package 'subgames' and
texture packages, for which a 'minetest-subgame-build-system' and
'minetest-texture-pack-build-system' build system could be defined.
It seemed a bit pointless to me to put those not-yet-defined build
systems in separate modules.
Greetings,
Maxime.
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 929 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]
next prev parent reply other threads:[~2023-02-04 14:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-03 17:11 Reducing useless module imports Julien Lepiller
2023-02-04 14:12 ` Maxime Devos [this message]
2023-02-11 23:32 ` [PATCH 0/3] Add '-Wunused-module' Ludovic Courtès
2023-02-11 23:32 ` [PATCH 1/3] Add -Wunused-module Ludovic Courtès
2023-02-11 23:32 ` [PATCH 2/3] Add 'record-case' to '.dir-locals.el' Ludovic Courtès
2023-02-11 23:32 ` [PATCH 3/3] Remove unnecessary module imports 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=997ca8a8-ac79-de44-fb84-958f514c75c9@telenet.be \
--to=maximedevos@telenet.be \
--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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.