all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: swedebugia <swedebugia@riseup.net>
To: Pierre Neidhardt <mail@ambrevar.xyz>,
	Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Help with sxml simple parser for the quicklisp importer
Date: Wed, 23 Jan 2019 22:21:42 +0100	[thread overview]
Message-ID: <961a50e7-b048-87d9-0881-e97ed1683dc1@riseup.net> (raw)
In-Reply-To: <87zhrrqjyy.fsf@ambrevar.xyz>

On 2019-01-23 19:58, Pierre Neidhardt wrote:
> 
> I'm not sure you need to extract Quickdocs data at all.  What Quickdocs does is
> all automated I believe, so you could probably do the same it's already doing:
> extract the metadata from the project themselves.
> 
> Most of the data is contained in the .asd files.  I think looking at Quickdocs
> code could be most informative, especially considering it's written in Common
> Lisp ;)
> 

You are right. And Ricardo. Quickdocs seems like a dirty hack. The 
information we want is in the tgz that we download so I just found out 
that we can do the same as with the pypi importer and extract it from 
there :)

The .asd files seem uniformly formatted.
-- 
Cheers
Swedebugia

  reply	other threads:[~2019-01-23 21:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-23 12:35 Help with sxml simple parser for the quicklisp importer swedebugia
2019-01-23 14:22 ` Ricardo Wurmus
2019-01-23 16:03   ` swedebugia
2019-01-23 15:58     ` Ricardo Wurmus
2019-01-23 16:32       ` swedebugia
2019-01-23 16:41         ` Ricardo Wurmus
2019-01-23 18:58           ` Pierre Neidhardt
2019-01-23 21:21             ` swedebugia [this message]
2019-01-23 16:55       ` Katherine Cox-Buday

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=961a50e7-b048-87d9-0881-e97ed1683dc1@riseup.net \
    --to=swedebugia@riseup.net \
    --cc=guix-devel@gnu.org \
    --cc=mail@ambrevar.xyz \
    --cc=rekado@elephly.net \
    /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.