From: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
To: Christopher Baines <mail@cbaines.net>
Cc: 60288@debbugs.gnu.org
Subject: [bug#60288] [RESEND #2] [PATCH v1 0/2] Start adding ZIM file(s)
Date: Mon, 2 Jan 2023 21:01:41 +0100 [thread overview]
Message-ID: <20230102210141.5aef6d97@primary_laptop> (raw)
In-Reply-To: <87bknn2y67.fsf@cbaines.net>
[-- Attachment #1: Type: text/plain, Size: 830 bytes --]
On Wed, 28 Dec 2022 18:10:54 +0000
Christopher Baines <mail@cbaines.net> wrote:>
> Maybe an alternative if you want to have a package would be to
> symlink to the source.
The issue is that I don't know how to refer to the source in a
situation like that.
I didn't really find good examples of all that. So far the best
I saw was to either define (source [...]) and reuse it in multiple
packages or to reuse the source of another package with (package-source
<package name>) like in linux.scm.
With the gnu build system, it copies the source in the current
directory, so I've really no idea what to do here. We might also need
to add the source to the inputs or native-inputs or propagated-inputs
somehow so it would not garbage collect it when we install the zim. Is
propagated-inputs the way to go?
Denis.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2023-01-02 20:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-23 22:07 [bug#60288] [RESEND #2] [PATCH v1 0/2] Start adding ZIM file(s) Denis 'GNUtoo' Carikli
2022-12-23 22:20 ` [bug#60288] [PATCH v1 1/2] build-system/copy: Add #:substitutable? argument Denis 'GNUtoo' Carikli
2022-12-23 22:20 ` [bug#60288] [PATCH v1 2/2] gnu: Add wikipedia_en_all_maxi Denis 'GNUtoo' Carikli
2022-12-28 18:10 ` [bug#60288] [RESEND #2] [PATCH v1 0/2] Start adding ZIM file(s) Christopher Baines
2022-12-29 23:19 ` Denis 'GNUtoo' Carikli
2023-01-02 20:01 ` Denis 'GNUtoo' Carikli [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=20230102210141.5aef6d97@primary_laptop \
--to=gnutoo@cyberdimension.org \
--cc=60288@debbugs.gnu.org \
--cc=mail@cbaines.net \
/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).