From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Andrew Miloradovsky <andrew@interpretmath.pw>,
34378-done@debbugs.gnu.org
Subject: bug#34378: update GNOME Planner to current
Date: Tue, 23 Aug 2022 14:55:14 -0400 [thread overview]
Message-ID: <87lereg57x.fsf_-_@gmail.com> (raw)
In-Reply-To: <87k1h5v2i6.fsf@gnu.org> ("Ludovic Courtès"'s message of "Mon, 11 Mar 2019 16:45:21 +0100")
Hello,
Ludovic Courtès <ludo@gnu.org> writes:
[...]
>>>> + ;;; 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?
>>
>> I picked that commit just because it was the most recent: the release is
>> expected to be very difficult to make, a lot of things need to be
>> fixed/modernized first, and there are not many people to review the
>> patches (one to be exact, AFAICT).
>>
>> I'm not sure there are really compelling reasons: most/all of the
>> changes made since the release are either about translations
>> (documentation generation is broken anyways), or fixes of deprecation
>> warnings (which otherwise would prevent it from building in Nixpkgs with
>> the default -Werror).
>
> OK. I think it’s a case where we’d wait for upstream to push a new
> release, rather than guess which commit is appropriate to distribute.
>
> Thoughts?
Agreed. Closing.
Maxim
prev parent reply other threads:[~2022-08-23 19:00 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
2019-02-13 13:13 ` Andrew Miloradovsky
2019-03-11 15:45 ` Ludovic Courtès
2022-08-23 18:55 ` Maxim Cournoyer [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=87lereg57x.fsf_-_@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=34378-done@debbugs.gnu.org \
--cc=andrew@interpretmath.pw \
--cc=ludo@gnu.org \
/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).