| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
|
| |
And display this on the package page.
This uses a couple of new tables, and an additional field in the
package_metadata table.
Currently, the order of the licenses in the package definition isn't stored,
as I'm not sure the order in the list is significant.
|
|
|
|
|
|
|
| |
Store the location a package can be found at, and display this on the package
page.
If available, link off to the git repository containing the package.
|
| |
|
|
|
|
|
| |
Lower powered devices will have problems displaying all ~9000+ packages, so
return a smaller number by default.
|
|
|
|
|
| |
This adds more query parameter validation, and uses form-horizontal-control to
neaten up the view code.
|
| |
|
|
|
|
|
|
| |
Add handling for some query parameters to the branch page. This takes
advantage of the improvements for building forms and query parameter
validation.
|
|
|
|
| |
Each input is pretty complex, and this function helps handle that complexity.
|
|
|
|
|
|
| |
Add some new pages /branches and /branch/... as well as a new git_branches
table. Also extend the email processing to enter the branch information in to
the database.
|
|
|
|
|
|
| |
Rather than just storing the URL in the guix_revisions and
load_new_guix_revision_jobs tables. This will help when storing more
information like tags and branches in the future.
|
|
|
|
| |
On the packages comparison page.
|
|
|
|
| |
To show the total number of derivations, and guix revisions.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
As this helps with the layout, especially the whitespace to the left
on smaller screens.
|
| |
|
|
|
|
|
| |
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.
|
| |
|
| |
|
| |
|
|
|
|
| |
For showing more information about builds, revisions and derivations.
|
|
|
|
| |
On the comparison page.
|
| |
|
|
|
|
|
| |
Both to the packages and derivations packages, as well as the JSON
representation of the pages.
|
|
|
|
|
| |
The primary use I have in mind for this is producing a list of strings
suitable for building a limited Cuirass job with.
|
|
|
|
|
| |
Previously, some extra data from the query would be added on to the
end of the version. This change prevents that from happening.
|
| |
|
| |
|
| |
|
|
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
|