Howdy!
Alex Sassmannshausen skribis:
> Christopher Baines writes:
[...]
>> So I've got an initial thing working for the version histories now. You
>> can construct a URL like [1], which will show a table about the known
>> versions of the package (icecat in this case) on the master branch.
Christopher Baines writes:
> Ludovic Courtès writes:
>
>> That would be great. In the end, it seems to be that there are quite a
>> few services we could build around the Data Service. I’m not sure how
>> they should interact.
>>
>> For instance, Mumi could talk to data.guix.gnu.org over an
Ludovic Courtès writes:
> That would be great. In the end, it seems to be that there are quite a
> few services we could build around the Data Service. I’m not sure how
> they should interact.
>
> For instance, Mumi could talk to data.guix.gnu.org over an HTTP API, or
> should we replicate
Hi Chris,
On Sat, 14 Sep 2019 at 12:52, Christopher Baines wrote:
> Accessing the history of package versions isn't possible yet, but this
> is something I can look at adding, the information is there in the
> database.
This should be awesome. :-)
It often arises when one wants to reproduce a
Ludovic Courtès writes:
> Hi Chris,
>
> Christopher Baines skribis:
>
>> For processing jobs, the records in the database used to be deleted when the
>> job was completed, but now the records are kept and there's a page showing
>> jobs [4].
>>
>> 4: http://milano-guix-1.di.unimi.it:8765/jobs
>
Hi Chris,
Christopher Baines skribis:
> For processing jobs, the records in the database used to be deleted when the
> job was completed, but now the records are kept and there's a page showing
> jobs [4].
>
> 4: http://milano-guix-1.di.unimi.it:8765/jobs
Nice! The page only shows completed
Hey,
I think I sent out the last update about the Guix Data Service back in May
[1], and quite a few things have changed since then. This is a summary of
changes since then, and a list of things that I'm interested in looking at
next.
1:
