Fwd: Re: quicklisp importer?

Fwd: Re: quicklisp importer?

[swedebugia]

Hi people

All details needed to create an importer should be available below.

Pierre asked off-list:
 > Swedebugia, would you like to give it a shot?  I can help of course.

Yes :) I will look into it, this seems easier now that I already learned 
to handle git and branches and also studied the pypi- and npm-importers.
:D

Cheers
swedebugia

-------- Forwarded Message --------
Subject: 	Re: quicklisp importer?
Date: 	Tue, 11 Dec 2018 06:05:56 -0800
From: 	Zach Beane <zach@quicklisp.org>
To: 	swedebugia@riseup.net
CC: 	mail@ambrevar.xyz





On Mon, Dec 10, 2018 at 11:04 PM <swedebugia@riseup.net 
<mailto:swedebugia@riseup.net>> wrote:

     Hi Zach

     Thank you! What a nice simple API (compared to what we deal with in
     other importers).

     On 2018-12-11 04:24, Zach Beane wrote:
      > One option is to start from here:
      >
      > https://beta.quicklisp.org/dist/quicklisp.txt
      >
      > From there, go to the release-index-url value, e.g.
      > https://beta.quicklisp.org/dist/quicklisp/2018-12-10/releases.txt

     This looks very good.

     Are the tarballs static or regenerated sometimes?
     Is the old tarballs for earlier releases available?


Tarballs are static and are never changed or deleted.

quicklisp.txt is updated periodically to point to new dist indexes. 
https://beta.quicklisp.org/dist/quicklisp-versions.txt has a list of 
active dist versions.


     file-md5 content-sha1 is the two file hashes.

     We strictly need sha256 because of the way the /gnu/store is 
implemented
     in Nix/Guix.
     Could you add that as an additional hash in the next release?


Look at digests.txt alongside releases.txt.

     Are all build time and run time dependencies?


Build time. Foreign libraries are not listed, sorry - and there are many 
that are required. I collect the data but do not currently publish it.

Zach

      > On Mon, Dec 10, 2018 at 4:41 PM <swedebugia@riseup.net
     <mailto:swedebugia@riseup.net>> wrote:
      >
      >> Hi
      >>
      >> I work on the guix project.
      >>
      >> We have importers for semi-automatic importing of packages from
      >> pypi,
      >> CRAN, etc.
      >>
      >> We currently lack a quicklisp importer.
      >>
      >> Would it be possible for you to help me understand the API or
      >> structure
      >> of Quicklisp Beta and the paths to files?
      >>
      >> Is there a list of packages somewhere?
      >>
      >> How can I map a package name to the newest version to the path for
      >> the
      >> tarball?
      >>
      >> Cheers
      >> swedebugia
      >>
      >> -------- Original Message --------
      >> Subject: Re: quicklisp importer?
      >> Date: 2018-12-11 00:10
      >> From: Pierre Neidhardt <mail@ambrevar.xyz
     <mailto:mail@ambrevar.xyz>>
      >> To: swedebugia@riseup.net <mailto:swedebugia@riseup.net>
      >> Cc: guix-devel <guix-devel@gnu.org <mailto:guix-devel@gnu.org>>
      >>
      >> Nope, Andy Patterson had some plans about it, but as far as I know,
      >> nothing has
      >> been done yet.
      >>
      >> I'd be very interested by a recursive importer as well! :)
      >>
      >> --
      >> Cheers
      >> Swedebugia

     --     Cheers
     Swedebugia