From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([209.51.188.92]:46870) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1h3NGh-0006eI-Pe for guix-patches@gnu.org; Mon, 11 Mar 2019 11:55:12 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1h3N7q-0001F9-RE for guix-patches@gnu.org; Mon, 11 Mar 2019 11:46:03 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:54063) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1h3N7q-0001Ez-Lh for guix-patches@gnu.org; Mon, 11 Mar 2019 11:46:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1h3N7q-0003Z4-E7 for guix-patches@gnu.org; Mon, 11 Mar 2019 11:46:02 -0400 Subject: [bug#34378] update GNOME Planner to current Resent-Message-ID: From: Ludovic =?UTF-8?Q?Court=C3=A8s?= References: <9bb349a5-a9a9-13b2-35c4-1ea63ffcbd43@interpretmath.pw> <87h8d8hdnw.fsf@gnu.org> <90daaef6-902f-f6a5-7cdb-9e3b162110c1@interpretmath.pw> Date: Mon, 11 Mar 2019 16:45:21 +0100 In-Reply-To: <90daaef6-902f-f6a5-7cdb-9e3b162110c1@interpretmath.pw> (Andrew Miloradovsky's message of "Wed, 13 Feb 2019 13:13:59 +0000") Message-ID: <87k1h5v2i6.fsf@gnu.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-patches-bounces+kyle=kyleam.com@gnu.org Sender: "Guix-patches" To: Andrew Miloradovsky Cc: 34378@debbugs.gnu.org Hi Andrew, Sorry for the loooong delay! Andrew Miloradovsky skribis: > On 2/12/19 9:58 PM, Ludovic Court=C3=A8s wrote: >> Hi Andrew, >> >> Andrew Miloradovsky skribis: >> >>> The release is fairly old and contains prebuilt scripts. >> What do you mean by =E2=80=9Cprebuilt scripts=E2=80=9D? > > By pre-built scripts I mean things like `configure`, generated by > auto-tools and gnome-common. Oh I see. We currently accept scripts generated by the Autotools (it=E2=80= =99s pretty much an exception in our policy; perhaps that=E2=80=99ll change in t= he future.) >>> + ;;; Warning: >>> + ;;; The documentation generation mechanism is long broken. No Yelp y= et. >>> + ;;; So the output doesn't contain any docs, unlike the ancient relea= se. >>> + ;;; OTOH, that's probably not a huge concern, given the circumstance= s. >>> + (let ((commit "fa7cbe309d5a705502ca46f808bcf78840804dbe") >>> + (revision "2019-02-08")) >> How did you pick this particular commit? In general we only package >> releases, unless there=E2=80=99s a compelling reason to build straight f= rom the >> VCS. Do you think that=E2=80=99s 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=E2=80=99s a case where we=E2=80=99d wait for upstream to pu= sh a new release, rather than guess which commit is appropriate to distribute. Thoughts? Thanks, Ludo=E2=80=99.