(define-module (gnu services science) #:export ( rshiny-configuration rshiny-configuration? rshiny-configuration-package rshiny-configuration-binary rshiny-shepherd-service rshiny-service-type)) (use-modules (gnu) (guix records) (ice-9 match)) (use-service-modules shepherd) (use-package-modules cran) (define-record-type* rshiny-configuration make-rshiny-configuration rshiny-configuration? (package rshiny-configuration-package ; package (default r-shiny)) (binary rshiny-configuration-binary ; string (default "rshiny"))) (define rshiny-shepherd-service (match-lambda (($ package binary) (list (shepherd-service (documentation (string-append "R-Shiny service for " binary)) (provision (list (symbol-append 'rshiny- (string->symbol (string-take binary 9))))) (requirement '(networking)) (start #~(exec-command (list #$(string-append "/run/current-system/profile/bin/" binary)) ;#:log-file #$(string-append "/var/log/" binary ".log") ; kills shepherd #:environment-variables (list "R_LIBS_USER=/run/current-system/profile/site-library/"))) (stop #~(make-kill-destructor))))))) (define rshiny-service-type (service-type (name 'rshiny) (extensions (list (service-extension shepherd-root-service-type rshiny-shepherd-service) (service-extension profile-service-type ;; We want the package installed so that it ;; pulls in the propagated inputs as well. (lambda (config) (list (rshiny-configuration-package config)))))) (description "Run an R-Shiny webapp as a Guix Service."))) b30f240b7b64c5666d8d5023c'>root/tests/guix-package-net.sh
AgeCommit message (Expand)Author
2022-01-19package: Honor '--dry-run' when target profile is already in store....Fixes <https://issues.guix.gnu.org/53267>. Reported by Tirifto <tirifto@posteo.cz>. Regression introduced in 65ffb9388c1c3d870cb07e4cb3ef12c9ac06a161. In the (unlikely) case where the profile we're targeting with "guix upgrade -n" or similar is already built, a new profile generation would be created and linked to despite the use of '-n'. This is because 65ffb9388c1c3d870cb07e4cb3ef12c9ac06a161 assumed that dry-run behavior would be handled solely by the build handler, which is not the case when there's nothing to build. * guix/scripts/package.scm (build-and-use-profile): Reintroduce #:dry-run? and honor it. (process-actions): Pass #:dry-run? to 'build-and-use-profile'. * tests/guix-package-net.sh: Add test. Ludovic Courtès
2022-01-16tests: Clean up after 'tests/guix-package-net.sh'....* tests/guix-package-net.sh: Remove second 'trap' line. Change first 'trap' line to remove "$module_dir" and *.lock files. Ludovic Courtès
2020-09-28tests: Simplify shell exit status negation;...* tests/guix-archive.sh, tests/guix-build-branch.sh, tests/guix-build.sh, tests/guix-daemon.sh, tests/guix-download.sh, tests/guix-environment.sh, tests/guix-gc.sh, tests/guix-git-authenticate.sh, tests/guix-graph.sh, tests/guix-hash.sh, tests/guix-lint.sh, tests/guix-pack-relocatable.sh, tests/guix-pack.sh, tests/guix-package-aliases.sh, tests/guix-package-net.sh, tests/guix-package.sh: Use the shell '!' keyword to negate command exit status in place of 'if ...; then false; else true; fi' Eric Bavier