From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=) Subject: Re: gnumaint changes Date: Thu, 12 Jul 2018 17:57:01 +0200 Message-ID: <87wou0tpki.fsf@gnu.org> References: <20180627082345.5a23mezrrltcdbnl@abyayala> <8736x7pu2k.fsf@gnu.org> <87h8lnoeti.fsf@gnu.org> <87lgahj206.fsf@gnu.org> <87fu0p5fpb.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:46554) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fddy3-0004Zm-DA for guix-devel@gnu.org; Thu, 12 Jul 2018 11:57:20 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fddy2-0003i2-2F for guix-devel@gnu.org; Thu, 12 Jul 2018 11:57:19 -0400 In-Reply-To: <87fu0p5fpb.fsf@gnu.org> (Mike Gerwitz's message of "Wed, 11 Jul 2018 22:51:44 -0400") List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Mike Gerwitz Cc: guix-devel@gnu.org, maintainers@gnu.org Hello, Mike Gerwitz skribis: >> It=E2=80=99d be nice if synopses and descriptions in the Womb could cont= ain >> Texinfo markup. >> >> In fact, perhaps it=E2=80=99d make sense to reverse the roles, i.e., hav= e the >> Womb take (some of its) descriptions from Guix? > > `blub' in pkgblurbs (which is what `official-description' uses) is > provided by package authors after they've been dubbed by rms. That is > in turn used on gnu.org. Consequently, I think it's best to have such > blurbs maintained independently of guix. I see, that makes sense. > What sort of Texinfo markup are you looking for, and are we talking > about the same field? What field does guix use for the synopsis? > Everything in rec/gnupackages.rec is handled by us at maintainers@, so > we can do whatever we want there. For packages we occasionally use Texinfo markup, typically ornaments like @code or @itemize bullet lists. Not every synopsis/description needs it, but it=E2=80=99s nice to be able to use it. > Do you have a couple examples of what you think would be beneficial to > pull form Guix? I'm certainly open to the idea where it makes sense; > there's no sense in us duplicating effort within GNU unnecessarily. I realize that Guix doesn=E2=80=99t have all GNU packages yet so in fact th= ere=E2=80=99s not so much to pull from at this point. I was suspecting blurbs are likely to be more up-to-date in Guix, but that=E2=80=99s very subjective, I don=E2=80=99t know if this is the case. > I'm also working on automating parts of our recordkeeping: in the next > few weeks, Womb will have up-to-date version information automatically > pulled from info-gnu release announcements; the FTP server; and a couple > websites where necessary, though I'll be manually committing it for the > first few months to verify that it is all working properly. So Guix > might also be able to depend on rec/gnupackages.rec for checking for new > releases as well, since unfortunately GNU doesn't mandate the use of the > FTP server, or even info-gnu (so releases are all over the place). The (guix gnu-maintenance) modules are tools to retrieve the latest version of a GNU package by traversing its ftp.gnu.org (or similar) directory. That=E2=80=99s something you might find useful. Here=E2=80=99s= an example: --8<---------------cut here---------------start------------->8--- scheme@(guile-user)> ,use(gnu packages gcc) scheme@(guile-user)> ,use(guix upstream) scheme@(guile-user)> (package-latest-release gcc (force %updaters)) $4 =3D #< package: "gcc" version: "8.1.0" urls: ("mirror:/= /gnu/gcc/gcc-8.1.0/gcc-8.1.0.tar.xz" "mirror://gnu/gcc/gcc-8.1.0/gcc-8.1.0.= tar.gz") signature-urls: ("mirror://gnu/gcc/gcc-8.1.0/gcc-8.1.0.tar.xz.sig"= "mirror://gnu/gcc/gcc-8.1.0/gcc-8.1.0.tar.gz.sig")> --8<---------------cut here---------------end--------------->8--- Or simply: --8<---------------cut here---------------start------------->8--- scheme@(guile-user)> ,use(guix gnu-maintenance) scheme@(guile-user)> (latest-release "emacs") $5 =3D #< package: "emacs" version: "26.1" urls: ("ftp://f= tp.gnu.org/gnu/emacs/emacs-26.1.tar.xz" "ftp://ftp.gnu.org/gnu/emacs/emacs-= 26.1.tar.gz") signature-urls: ("ftp://ftp.gnu.org/gnu/emacs/emacs-26.1.tar.= xz.sig" "ftp://ftp.gnu.org/gnu/emacs/emacs-26.1.tar.gz.sig")> --8<---------------cut here---------------end--------------->8--- This relies primarily on . Packages not hosted on gnu.org are typically annotated with the download URL such that the update-checking code does the right thing. Thanks, Ludo=E2=80=99.