From: Mike Gerwitz <mtg@gnu.org>
To: guix-devel@gnu.org
Subject: Re: gnumaint changes
Date: Wed, 27 Jun 2018 21:55:05 -0400 [thread overview]
Message-ID: <87h8lnoeti.fsf@gnu.org> (raw)
In-Reply-To: <8736x7pu2k.fsf@gnu.org> (Mike Gerwitz's message of "Wed, 27 Jun 2018 21:40:19 -0400")
[-- Attachment #1: Type: text/plain, Size: 1255 bytes --]
On Wed, Jun 27, 2018 at 21:40:19 -0400, Mike Gerwitz wrote:
> I'll have to look at what guix/gnu-maintenance.scm does, but:
[...]
> Rather than get rid of gnupackages.txt completely, I wrote a script last
> week to generate it from rec/gnupackages.rec. The formats are largely
> the same---it's possible that you can use the recfile directly.
> However, if you still need the old format, just run
> `make gnupackages.txt`.
Ah, I see, it fetches that single file over HTTP. Certainly running
`make` (or the underlying gawk script) is undesirable in that situation.
Can someone with more knowledge of what this is used for run a couple of
tests to see what is broken if you use rec/gnupackages.rec instead?
Worst case, I can commit gnupackages.txt until the script can be
updated, but I'd prefer to keep generated files out of the repository.
pkgblurbs.txt has also been replaced by rec/pkgblurbs.rec.
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.
--
Mike Gerwitz
Free Software Hacker+Activist | GNU Maintainer & Volunteer
GPG: D6E9 B930 028A 6C38 F43B 2388 FEF6 3574 5E6F 6D05
https://mikegerwitz.com
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]
next prev parent reply other threads:[~2018-06-28 1:55 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 [this message]
2018-07-11 14:11 ` Ludovic Courtès
2018-07-12 2:51 ` Mike Gerwitz
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h8lnoeti.fsf@gnu.org \
--to=mtg@gnu.org \
--cc=guix-devel@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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.