From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=) Subject: Re: Synchronizing synopses with the Womb Date: Sat, 20 Apr 2013 15:46:12 +0200 Message-ID: <87vc7h9uxn.fsf@gnu.org> References: <201304182239.r3IMdF0P032258@freefriends.org> <87sj2myh5w.fsf@gnu.org> <87mwsusicm.fsf@naga.invergo.net> <87a9otd17m.fsf@gnu.org> <8761zhsc3n.fsf@naga.invergo.net> <87vc7hqxev.fsf@naga.invergo.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([208.118.235.92]:55844) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UTY7V-00038m-9x for bug-guix@gnu.org; Sat, 20 Apr 2013 09:46:26 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UTY7U-0001yy-EA for bug-guix@gnu.org; Sat, 20 Apr 2013 09:46:25 -0400 In-Reply-To: <87vc7hqxev.fsf@naga.invergo.net> (Brandon Invergo's message of "Sat, 20 Apr 2013 13:00:40 +0200") List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org To: Brandon Invergo Cc: bug-guix@gnu.org Brandon Invergo skribis: >> Is there any easy way to extract long descriptions from GSRC? There >> could be a script in Guix, similar to what we have for the Womb. I >> suspect it might be a bit more work, though. > > I took inspiration from you guys and made a way to output package > information in the Recutils recfile format. An entire package manifest > in recfile format can be made with "make manifest" in the top-level GSRC > directory (it's also included by default in the last distribution, > gsrc-2013-04-06.tar.gz, but I recommend checking out the bzr repo). Great. I was able to build it (with $srcdir =3D $buildir). Is there a place on-line where a pre-built MANIFEST.rec is/could be made available? That would simplify automation on the Guix side (for the Womb, we just take gnupackages.txt from CVSWeb.) [...] > Of course, I welcome any suggested changes or corrections to the > descriptions. As you can imagine, doing a marathon of describing > hundreds of GNU packages alone might have led to some poor wording in > places. How do you usually come up with those descriptions? I typically take a paragraph or two from the package=E2=80=99s home page. Thanks! Ludo=E2=80=99.