Re: mirror://gnome question
On Sat, Feb 29, 2020 at 7:34 PM Leo Famulari wrote: > These URLs provide content-addressed mirrors that Guix always falls back to > when it cannot download the file in the "normal" way, which in that case > would be the GNOME mirrors. They are defined in 'guix/download.scm'. Thanks for the details, I'll have a look -- Vincent Legoll
Re: Thoughts on making Guix even better
Hello Leo! > This is not as much a guix package vs. guix system issue as it is an > issue of explicit manifests against implicit ones. If you use guix > package with manifests and without inferiors, you will have the same > problem. Likewise, you can use inferiors in your config.scm to > mitigate some of those issues. At least it works for the kernel, but > it should in theory also work for packages. I see. > PS: What you're envisioning is probably a front-end, that obscures the > very existence of a config.scm by managing one that is just as verbose > as guix-generated manifests are. However, this is not really a > solution as it fails to address the need for a (human-readable) initial > configuration. The interface would also be a pain to deal with as each > service comes with its own configuration record allowing arbitrary lisp > expressions that one would have to write on the command line. I think we can still maintain the guix way of doing config.scm and also bring modularity. My thought is, what if we could split the operating-system procedures into smaller procedures, such as, kernel, system-wide packages, services etc. into separate procedures? So if a user passes the procedure name to the `guix system reconfigure` command, then only that procedure is reconfigured. For example, we can reconfigure kernel of the system without reconfiguring packages and services. What do you think? Regards, RG.
gwl-0.2.1 released [stable]
We are pleased to announce the release of the GNU Guix Workflow Language version 0.2.1, representing 23 commits by one person. This is a bug-fix release to correct a few annoying bugs that went unnoticed in the previous release. One of the fixes unlocks the process output cache, which was added in 0.2.0 but was always disabled. • About The Guix Workflow Language (GWL) provides an extension to GNU Guix's declarative language for package management to automate the execution of programs in scientific workflows. The GWL can use process engines to integrate with various computing environments. • Download Here are the compressed sources and a GPG detached signature[*]: https://ftpmirror.gnu.org/gwl/gwl-0.2.1.tar.gz https://ftpmirror.gnu.org/gwl/gwl-0.2.1.tar.gz.sig Use a mirror for higher download bandwidth: https://www.gnu.org/order/ftp.html [*] Use a .sig file to verify that the corresponding file (without the .sig suffix) is intact. First, be sure to download both the .sig file and the corresponding tarball. Then, run a command like this: gpg --verify gwl-0.2.1.tar.gz.sig If that command fails because you don't have the required public key, then run this command to import it: gpg --keyserver keys.gnupg.net --recv-keys BCA689B636553801C3C62150197A5888235FACAC and rerun the 'gpg --verify' command. This release was bootstrapped with the following tools: Autoconf 2.69 Automake 1.16.1 Gnulib v0.1-3269-g03d7a6b1f • Changes in 0.2.1 (since 0.2.0) ** Documentation - additional documentation of the “run-time” field and the “complexity” type - added example of how to use =pick= with local variable definitions ** Bug fixes - due to a faulty condition (a test whether a file is a directory), process outputs were never cached. The condition has been corrected. - outputs with absolute file names are no longer considered missing - workflows without inputs no longer trigger an error signature.asc Description: PGP signature
