From: "Ludovic Courtès" <ludo@gnu.org>
To: Andrew Miloradovsky <andrew@interpretmath.pw>
Cc: 34378@debbugs.gnu.org
Subject: [bug#34378] update GNOME Planner to current
Date: Tue, 12 Feb 2019 22:58:43 +0100 [thread overview]
Message-ID: <87h8d8hdnw.fsf@gnu.org> (raw)
In-Reply-To: <9bb349a5-a9a9-13b2-35c4-1ea63ffcbd43@interpretmath.pw> (Andrew Miloradovsky's message of "Fri, 8 Feb 2019 01:54:08 +0000")
Hi Andrew,
Andrew Miloradovsky <andrew@interpretmath.pw> 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 <andrew@interpretmath.pw>
> 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’.
next prev parent reply other threads:[~2019-02-12 21:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-08 1:54 [bug#34378] update GNOME Planner to current Andrew Miloradovsky
2019-02-12 21:58 ` Ludovic Courtès [this message]
2019-02-13 13:13 ` Andrew Miloradovsky
2019-03-11 15:45 ` Ludovic Courtès
2022-08-23 18:55 ` bug#34378: " Maxim Cournoyer
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=87h8d8hdnw.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=34378@debbugs.gnu.org \
--cc=andrew@interpretmath.pw \
/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).