From: Maxime Devos <maximedevos@telenet.be>
To: Zac Berkowitz <zac.berkowitz@gmail.com>
Cc: 55874@debbugs.gnu.org
Subject: [bug#55874] [PATCH] Add timewarrior 1.4.3
Date: Fri, 10 Jun 2022 16:54:15 +0200 [thread overview]
Message-ID: <6590de620d1c20115e12eafcacddb7637d903a9e.camel@telenet.be> (raw)
In-Reply-To: <CANNGBfkndu19UdqkeMBwjWhDWcUzwS2mb08O4EFtnt0BJ4yweA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1314 bytes --]
Zac Berkowitz schreef op vr 10-06-2022 om 10:04 [-0400]:
> The python scripts in ext/ are completely optional according to the
> README in that same directory. Like taskwarrior, timewarrior can
> execute python scripts as hooks in response to various commands, but
> they're not necessary for base use.
> Maybe this is why debian adds the python requirement? So hooks just
> work out of the box? How does guix deal with optional dependencies
> like this?
>
If it increases the closure size a lot and does not provide much extra
functionality, the extra dependency (and the components that require
that dependency) is removed. (Alternatively the ext/ scripts can be
changed to use the 'python' in $PATH instead of a baked-in 'python',
though such things are avoided where feasible for robustness).
Even if they are optional, adding python might be required such that
the _correct_ python is used when cross-compiling. As a test, you
could try running "guix gc --references" on the timewarrior store item
-- if the output contains python, the ext/... is installed with python.
Probably most people would have python anyway, so I don't think it has
to be removed.
Looking at the output of "guix gc --references", it does indeed use
python from somewhere.
Greetings,
Maxime.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2022-06-10 14:55 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-09 15:11 [bug#55874] [PATCH] Add timewarrior 1.4.3 Zac Berkowitz
2022-06-09 19:50 ` Maxime Devos
2022-06-09 19:53 ` Maxime Devos
2022-06-09 19:55 ` Maxime Devos
2022-06-09 19:56 ` Maxime Devos
2022-06-09 20:01 ` Maxime Devos
2022-06-09 20:06 ` Maxime Devos
2022-06-09 20:08 ` Maxime Devos
2022-06-09 20:09 ` Maxime Devos
2022-06-09 20:10 ` Maxime Devos
2022-06-09 20:12 ` Maxime Devos
2022-06-09 20:17 ` Maxime Devos
2022-06-10 1:36 ` Zac Berkowitz
2022-06-10 7:49 ` Maxime Devos
2022-06-10 14:04 ` Zac Berkowitz
2022-06-10 14:54 ` Maxime Devos [this message]
2022-06-10 14:56 ` Maxime Devos
2022-06-10 15:00 ` Maxime Devos
2022-06-10 15:00 ` Maxime Devos
2022-06-13 18:14 ` [bug#55874] [PATCH v2] " Zac Berkowitz
2023-01-28 10:08 ` bug#55874: " Nicolas Goaziou
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=6590de620d1c20115e12eafcacddb7637d903a9e.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=55874@debbugs.gnu.org \
--cc=zac.berkowitz@gmail.com \
/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).