From mboxrd@z Thu Jan 1 00:00:00 1970 From: Brandon Invergo Subject: Re: Synchronizing synopses with the Womb Date: Sat, 20 Apr 2013 13:00:40 +0200 Message-ID: <87vc7hqxev.fsf@naga.invergo.net> References: <201304182239.r3IMdF0P032258@freefriends.org> <87sj2myh5w.fsf@gnu.org> <87mwsusicm.fsf@naga.invergo.net> <87a9otd17m.fsf@gnu.org> <8761zhsc3n.fsf@naga.invergo.net> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([208.118.235.92]:46516) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UTVXF-0000JK-7M for bug-guix@gnu.org; Sat, 20 Apr 2013 07:00:51 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UTVXC-0006Ei-DH for bug-guix@gnu.org; Sat, 20 Apr 2013 07:00:49 -0400 Received: from fencepost.gnu.org ([2001:4830:134:3::e]:55905) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UTVXC-0006EX-2c for bug-guix@gnu.org; Sat, 20 Apr 2013 07:00:46 -0400 Received: from [95.61.26.193] (port=46280 helo=localhost) by fencepost.gnu.org with esmtpsa (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1UTVXA-0002qQ-MR for bug-guix@gnu.org; Sat, 20 Apr 2013 07:00:45 -0400 In-Reply-To: <8761zhsc3n.fsf@naga.invergo.net> (Brandon Invergo's message of "Sat, 20 Apr 2013 12:58:04 +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: bug-guix@gnu.org --=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Hmm...not sure what I did to add all those funny characters to the email. I'll fix it: > 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). Once MANIFEST.rec has been built, it is simple to get the info with recsel. The field "Garname" contains the simple one-word package name (always the same name used in forming URLs on the GNU web and FTP sites and, i.e. at http://www.gnu.org/software/$Garname). The long description is contained in the "Blurb" field. $ recsel -e "Garname =3D 'hello'" -P "Blurb" MANIFEST.rec GNU Hello prints the message "Hello, world!" and then exits. It serves as an example of standard GNU coding practices. As such, it supports command-line arguments, multiple languages, and so on. $ recsel -e "Garname 'src-highlite'" -P "Blurb" MANIFEST.rec Source-highlight reads in a source code file and produces an output file in which the keywords are highlighted in different colors to designate their syntactic role. It supports over 150 different languages and it can output to 8 different formats, including HTML, LaTeX and ODF. It can also output to ANSI color escape sequences, allowing, for example, GNU less to show highlighted source code. 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. I'll get to work on changing the short descriptions to match those of Womb... =2D-=20 Brandon Invergo http://brandon.invergo.net --=-=-= Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iQEcBAEBAgAGBQJRcnVbAAoJEARu3ubrerdNtGQH/128o+EYupJpAFeiIsP39L4b RYAAI6q0s5OAlMPyNfNtt2gIAcesiWr0IfjYBhVw9gs/6U6iXRzEPTXFOtKv90fx Hzbj2aLjw7uKg3fJ+rifulZ0BV7YtxBA/xEQbVODXPV62D1cpVVTHbXdLG7EKie3 dHCZ1c70etP5coZQiNoHQcbZGkCDXDpHdAL7aZH5PYORgvWlVrWuqMV/BXDNNFfT QuQsQUWuPCc68KtTY1tHle6mwCE0t2ret36WIBMZ04B5oj4CZcrGdZOxQK/wkddS 9ldAB2Rx3qqgXnMlTUCrs6rWFcIvMb7Q0+AhnVN6d1GhnbHQbARCp6SLnAOjkMU= =0vqU -----END PGP SIGNATURE----- --=-=-=--