| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
| |
Add tests around the package module, extract out the use of the
inferior-package record assessors so that they aren't part of the tests, and
switch across the package-metadata module to use
insert-missing-data-and-return-all-ids.
|
|
|
|
| |
By using insert-missing-data-and-return-all-ids.
|
|
|
|
|
| |
This is mostly for the JSON output, as it allows much more information to be
included.
|
| |
|
|
|
|
|
| |
Lower powered devices will have problems displaying all ~9000+ packages, so
return a smaller number by default.
|
|
|
|
|
| |
This can happen when the same package is defined with two names, for example,
with deprecated-package.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
For showing more information about builds, revisions and derivations.
|
|
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
|