guix
/
data-service
mirror of git://git.savannah.gnu.org/guix/data-service.git
2
0
Fork 0
Code Issues Releases Wiki Activity
data-service/Makefile.am

85 lines
3.1 KiB
Makefile
Raw Normal View History

Initial commit 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
2019-02-06 17:14:44 +01:00
# guix-data-service - Mediocre, uh, mail interface
# Copyright © 2016, 2017, 2018 Ricardo Wurmus <rekado@elephly.net>
# Copyright © 2019 Christopher Baines <mail@cbaines.net>
#
# This file is part of guix-data-service.
#
# guix-data-service is free software; you can redistribute it and/or modify it
# under the terms of the GNU General Public License as published by
# the Free Software Foundation; either version 3 of the License, or
# (at your option) any later version.
#
# guix-data-service is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with the guix-data-service. If not, see
# <http://www.gnu.org/licenses/>.
include guile.am
Add support for processing branch updated emails
2019-03-19 21:18:09 +01:00
bin_SCRIPTS = \
scripts/guix-data-service \
scripts/guix-data-service-process-jobs \
scripts/guix-data-service-process-branch-updated-email \
Add functionality to query build servers
2019-03-06 23:56:54 +01:00
scripts/guix-data-service-query-build-servers
Initial commit 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
2019-02-06 17:14:44 +01:00
moddir = $(prefix)/share/guile/site/$(GUILE_EFFECTIVE_VERSION)
godir = $(moddir)
assetsdir = $(datadir)/@PACKAGE@
Many changes 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.
2019-03-11 23:11:14 +01:00
SOURCES = \
Add support for processing branch updated emails
2019-03-19 21:18:09 +01:00
guix-data-service/branch-updated-emails.scm \
Many changes 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.
2019-03-11 23:11:14 +01:00
guix-data-service/builds.scm \
guix-data-service/comparison.scm \
guix-data-service/config.scm \
Extract out some database functionality to another module
2019-04-14 11:04:19 +02:00
guix-data-service/database.scm \
Many changes 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.
2019-03-11 23:11:14 +01:00
guix-data-service/jobs.scm \
guix-data-service/jobs/load-new-guix-revision.scm \
guix-data-service/model/build-server.scm \
guix-data-service/model/build-status.scm \
guix-data-service/model/build.scm \
guix-data-service/model/derivation.scm \
Start to handle information about Git branches 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.
2019-05-05 21:06:28 +02:00
guix-data-service/model/git-branch.scm \
Switch to storing Git repositories in a table 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.
2019-05-05 14:35:48 +02:00
guix-data-service/model/git-repository.scm \
Many changes 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.
2019-03-11 23:11:14 +01:00
guix-data-service/model/guix-revision-package-derivation.scm \
guix-data-service/model/guix-revision.scm \
Store license information for packages 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.
2019-05-15 09:05:14 +02:00
guix-data-service/model/license.scm \
guix-data-service/model/license-set.scm \
Store and display the location of packages 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.
2019-05-13 22:02:53 +02:00
guix-data-service/model/location.scm \
Many changes 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.
2019-03-11 23:11:14 +01:00
guix-data-service/model/package-derivation.scm \
guix-data-service/model/package-metadata.scm \
guix-data-service/model/package.scm \
guix-data-service/model/utils.scm \
guix-data-service/web/controller.scm \
guix-data-service/web/render.scm \
guix-data-service/web/server.scm \
guix-data-service/web/sxml.scm \
Add a new query-parameters module The query parameters feed in to the results shown, but also forms on pages. Validation is important to avoid errors and security issues, but it's also important to provide appropriate feedback to the user. This module provides some utilities and structure around handling query parameters.
2019-05-11 17:44:17 +02:00
guix-data-service/web/query-parameters.scm \
Many changes 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.
2019-03-11 23:11:14 +01:00
guix-data-service/web/util.scm \
Add a (tests driver) module Using the test driver from build-aux/test-driver.scm, as this shows the test errors when tests fail.
2019-05-12 17:58:22 +02:00
guix-data-service/web/view/html.scm \
Add a mock-inferior module This to help test code which uses the (guix inferior) module.
2019-05-12 17:58:56 +02:00
tests/driver.scm \
tests/mock-inferior.scm
Add an initial test Along with the buildsystem changes to make `make check` work.
2019-04-14 11:08:11 +02:00
TEST_EXTENSIONS = .scm
Add some missing test files to Makefile.am
2019-06-02 17:19:06 +02:00
TESTS = \
tests/branch-updated-emails.scm \
Add a new test to cover some of the loading new revisions code
2019-06-02 23:02:12 +02:00
tests/jobs-load-new-guix-revision.scm \
Add some missing test files to Makefile.am
2019-06-02 17:19:06 +02:00
tests/model-derivation.scm \
tests/model-git-branch.scm \
tests/model-git-repository.scm \
tests/model-license-set.scm \
tests/model-license.scm \
tests/model-package-metadata.scm
Add an initial test Along with the buildsystem changes to make `make check` work.
2019-04-14 11:08:11 +02:00
AM_TESTS_ENVIRONMENT = abs_top_srcdir="$(abs_top_srcdir)"
SCM_LOG_DRIVER = $(top_builddir)/test-env \
$(GUILE) --no-auto-compile -e main \
$(top_srcdir)/build-aux/test-driver.scm
AM_SCM_LOG_DRIVER_FLAGS = --brief=yes