| Commit message (Collapse) | Author | Age |
|---|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
In cases where the version is changed for example, the relevant derivations
will now show up, whereas previously they did not.
|
| |
|
|
|
| |
Rather than vhashes. This removes the need for the expensive vhash-delete
calls.
|
| | |
|
| |
|
|
|
|
| |
An empty list of derivation-file-names should result in no results,
but in the case of the systems, targets and build-statuses, we want
all of the results.
|
| |
|
|
|
| |
Add support for filtering the results, and add the system and target
to the output.
|
| | |
|
| |
|
|
| |
For the new and removed package sections.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
A large proportion of these changes relate to changing the way
packages relate to derivations. Previously, a package at a given
revision had a single derivation. This was OK, but didn't account for
multiple architectures.
Therefore, these changes mean that a package has multiple derivations,
depending on the system of the derivation, and the target system.
There are multiple changes, small and large to the web interface as
well. More pages link to each other, and the visual display has been
improved somewhat.
|
| |
|
|
| |
On the comparison page.
|
| | |
|
| |
|
|
|
|
| |
These changes mean that more information about derivations is
recorded. There are a number of corresponding changes in the database
schema that are not tracked in the repository unfortunately.
|
|
|
This is a service designed to provide information about Guix. At the
moment, this initial prototype gathers up information about packages,
the associated metadata and derivations.
The initial primary use case is to compare two different revisions of
Guix, detecting which packages are new, no longer present, updated or
otherwise different.
It's based on the Mumi project.
[1]: https://git.elephly.net/software/mumi.git
|