unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Mike Gerwitz <mtg@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org, maintainers@gnu.org
Subject: Re: gnumaint changes
Date: Wed, 11 Jul 2018 22:51:44 -0400	[thread overview]
Message-ID: <87fu0p5fpb.fsf@gnu.org> (raw)
In-Reply-To: 87lgahj206.fsf@gnu.org

[-- Attachment #1: Type: text/plain, Size: 2300 bytes --]

On Wed, Jul 11, 2018 at 16:11:37 +0200, Ludovic Courtès wrote:
> Hello Mike,
>
> Mike Gerwitz <mtg@gnu.org> skribis:

[...]

>> pkgblurbs.txt has also been replaced by rec/pkgblurbs.rec.
>
> Commit daf76c7cd54df428abc28d490747c7f83a844df0 changes
> gnu-maintenance.scm to use the .rec files.  Thanks for the heads-up.

Thanks.  I was planning to submit a patch this weekend, but you beat me
to it.  Sorry for the trouble!  I'm glad to see that the change was
pretty simple.

>> If anyone here also knows of any other external systems pulling from
>> womb, please lmk.  I wasn't aware that anyone outside of maintainers@
>> used that repo, tbh.
>
> It’s used by ‘guix import gnu’ and ‘guix lint -c gnu-descriptions’
> currently.
>
> It’d be nice if synopses and descriptions in the Womb could contain
> Texinfo markup.
>
> In fact, perhaps it’d make sense to reverse the roles, i.e., have 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.

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.

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'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).

-- 
Mike Gerwitz

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]

  reply	other threads:[~2018-07-12  2:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-27  8:23 gnumaint changes Nils Gillmann
2018-06-27 20:36 ` Ludovic Courtès
2018-06-28  4:52   ` Nils Gillmann
2018-06-28  1:40 ` Mike Gerwitz
2018-06-28  1:55   ` Mike Gerwitz
2018-07-11 14:11     ` Ludovic Courtès
2018-07-12  2:51       ` Mike Gerwitz [this message]
2018-07-12 15:57         ` Ludovic Courtès
2018-07-12 16:32           ` Mike Gerwitz
2018-07-13 10:24             ` Nils Gillmann
2018-07-13 12:01             ` Ludovic Courtès

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=87fu0p5fpb.fsf@gnu.org \
    --to=mtg@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=ludo@gnu.org \
    --cc=maintainers@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).