[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug#34378] update GNOME Planner to current
From: |
Ludovic Courtès |
Subject: |
[bug#34378] update GNOME Planner to current |
Date: |
Tue, 12 Feb 2019 22:58:43 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux) |
Hi Andrew,
Andrew Miloradovsky <address@hidden> skribis:
> The release is fairly old and contains prebuilt scripts.
What do you mean by “prebuilt scripts”?
> From cbe5c7a354381c665735085a5eb262404e901385 Mon Sep 17 00:00:00 2001
> From: Andrew Miloradovsky <address@hidden>
> Date: Fri, 8 Feb 2019 00:03:48 +0000
> Subject: [PATCH] gnu: gnome-planner: update 0.14.6 to 2019-02-08
>
> Build all from a modern version, enable Python bindings.
>
> * gnu/packages/gnome.scm (gnome-planner):
> - Fetch the sources from GNOME's own GitLab.
> - Run `autogen.sh` with the proper shell paths.
> - Enable Python 2 bindings, because we can now.
> - Add all the inputs necessary for all of that.
Please see ‘git log’ and
<https://www.gnu.org/software/guix/manual/en/html_node/Submitting-Patches.html>
for examples of the commit message format.
> + ;;; Warning:
> + ;;; The documentation generation mechanism is long broken. No Yelp yet.
> + ;;; So the output doesn't contain any docs, unlike the ancient release.
> + ;;; OTOH, that's probably not a huge concern, given the circumstances.
> + (let ((commit "fa7cbe309d5a705502ca46f808bcf78840804dbe")
> + (revision "2019-02-08"))
How did you pick this particular commit? In general we only package
releases, unless there’s a compelling reason to build straight from the
VCS. Do you think that’s the case here?
Thanks for the patch!
Ludo’.