guix-commits
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

branch master updated: website: Add draft of 1.3.0 release announcement.


From: Ludovic Courtčs
Subject: branch master updated: website: Add draft of 1.3.0 release announcement.
Date: Mon, 10 May 2021 09:15:16 -0400

This is an automated email from the git hooks/post-receive script.

civodul pushed a commit to branch master
in repository guix-artwork.

The following commit(s) were added to refs/heads/master by this push:
     new 0e3a67f  website: Add draft of 1.3.0 release announcement.
0e3a67f is described below

commit 0e3a67f12393486174a15cdf596a29881409922e
Author: Ludovic Courtès <ludo@gnu.org>
AuthorDate: Mon May 10 15:14:55 2021 +0200

    website: Add draft of 1.3.0 release announcement.
    
    * website/drafts/gnu-guix-1.3.0-released.md: New file.
---
 website/drafts/gnu-guix-1.3.0-released.md | 161 ++++++++++++++++++++++++++++++
 1 file changed, 161 insertions(+)

diff --git a/website/drafts/gnu-guix-1.3.0-released.md 
b/website/drafts/gnu-guix-1.3.0-released.md
new file mode 100644
index 0000000..9e063ba
--- /dev/null
+++ b/website/drafts/gnu-guix-1.3.0-released.md
@@ -0,0 +1,161 @@
+title: GNU Guix 1.3.0 released
+date: 2021-05-11 14:00:00
+author: Ludovic Courtès
+slug: gnu-guix-1.3.0-released
+tags: Releases, Security
+---
+FIXME: Use 1.3.0 test pilot.
+![Image of a flight of the 
Guix.](https://guix.gnu.org/static/blog/img/flight-of-the-guix.jpg)
+
+We are pleased to announce the release of GNU Guix version 1.3.0!
+
+The release comes with [ISO-9660 installation
+images](https://guix.gnu.org/manual/en/html_node/System-Installation.html),
+a [virtual machine
+image](https://guix.gnu.org/manual/en/html_node/Running-Guix-in-a-VM.html),
+and with tarballs to install the package manager on top of your
+GNU/Linux distro, either [from
+source](https://guix.gnu.org/manual/en/html_node/Requirements.html) or
+[from
+binaries](https://guix.gnu.org/manual/en/html_node/Binary-Installation.html).
+Guix users can update by running `guix pull`.
+
+It’s been almost 6 months since the last release, during which 212
+people contributed code and packages, and a number of people contributed
+to other important tasks—code review, system administration,
+translation, web site updates, Outreachy mentoring, and more.
+
+There’s been more than 8,300 commits in that time frame, which we’ll
+humbly try to summarize in these release notes.
+
+### User experience
+
+A distinguishing Guix feature is its support for _declarative
+deployment_: instead of running a bunch of `guix install` and `guix
+remove` commands, you run `guix package --manifest=manifest.scm`, where
+`manifest.scm` lists the software you want to install in a snippet that
+looks like this:
+
+```scheme
+;; This is 'manifest.scm'.
+(specifications->manifest
+  (list "emacs" "guile" "gcc-toolchain"))
+```
+
+Doing that installs exactly the packages listed.  You can have that file
+under version control and share it with others, which is convenient.
+Until now, one would have to write the manifest by hand—not
+insurmountable, but still a barrier to someone willing to migrate to the
+declarative model.
+
+The [new `guix package --export-manifest`
+command](https://guix.gnu.org/manual/en/html_node/Invoking-guix-package.html)
+(and its companion `--export-channels` option) produces a manifest based
+on the contents _of an existing profile_.  That makes it easy to
+transition from the classic “imperative” model, where you run `guix
+install` as needed, to the more formal declarative model.  This was long
+awaited!
+
+Users who like to always run the latest and greatest pieces of the free
+software commons will love [the new `--with-latest` package
+transformation
+option](https://guix.gnu.org/manual/en/html_node/Package-Transformation-Options.html).
+Using the same code as [`guix
+refresh`](https://guix.gnu.org/manual/en/html_node/Invoking-guix-refresh.html),
+this option looks for the latest _upstream_ release of a package,
+fetches it, authenticates it, and builds it.  This is useful in cases
+where the new version is not yet packaged in Guix.  For example, the
+command below, if run today, will (attempt to) install QEMU 6.0.0:
+
+```
+$ guix install qemu --with-latest=qemu 
+The following package will be upgraded:
+   qemu 5.2.0 → 6.0.0
+
+Starting download of /tmp/guix-file.eHO6MU
+From https://download.qemu.org//qemu-6.0.0.tar.bz2...
+ …0.tar.bz2  123.3MiB                                                          
                                                            28.2MiB/s 00:04 
[##################] 100.0%
+
+Starting download of /tmp/guix-file.9NRlvT
+From https://download.qemu.org//qemu-6.0.0.tar.bz2.sig...
+ …tar.bz2.sig  310B                                                            
                                                             1.2MiB/s 00:00 
[##################] 100.0%
+gpgv: Signature made Thu 29 Apr 2021 09:28:25 PM CEST
+gpgv:                using RSA key CEACC9E15534EBABB82D3FA03353C9CEF108B584
+gpgv: Good signature from "Michael Roth <michael.roth@amd.com>"
+gpgv:                 aka "Michael Roth <mdroth@utexas.edu>"
+gpgv:                 aka "Michael Roth <flukshun@gmail.com>"
+The following derivation will be built:
+   /gnu/store/ypz433vzsbg3vjp5374fr9lhsm7jjxa4-qemu-6.0.0.drv
+
+…
+```
+
+There’s one obvious caveat: this is not guaranteed to work.  If the new
+version has a different build system, or if it requires extra
+dependencies compared to the version currently packaged, the build
+process will fail.  Yet, it provides users with additional flexibility
+which can be convenient at times.  For developers, it’s also a quick way
+to check whether a given package successfully builds against the latest
+version of one of its dependencies.
+
+Several changes were made here and there to improve user experience.  As
+an example, a [new `--verbosity`
+level](https://guix.gnu.org/manual/devel/en/html_node/Common-Build-Options.html)
+was added.  By default (`--verbosity=1`), fewer details about downloads
+get printed, which matches the expectation of most users.
+
+Another handy improvement is _suggestions_ when making typos:
+
+```
+$ guix package --export-manifests
+guix package: error: export-manifests: unrecognized option
+hint: Did you mean `export-manifest'?
+
+$ guix remve vim
+guix: remve: command not found
+hint: Did you mean `remove'?
+
+Try `guix --help' for more information.
+```
+
+People setting up [build offloading over
+SSH](https://guix.gnu.org/manual/en/html_node/Daemon-Offload-Setup.html)
+will enjoy the simplified process, where the `guile` executable no
+longer needs to be in `PATH`, with appropriate `GUILE_LOAD_PATH`
+settings, on target machines.  Instead, offloading now channels all its
+operations through `guix repl`.
+
+### Developer tools
+
+We have good news for packagers!  First, [`guix
+import`](https://guix.gnu.org/manual/en/html_node/Invoking-guix-import.html)
+comes with a new Go recursive importer, that can create package
+definitions or templates thereof for whole sets of Go packages.  The
+`guix import crate` command, for Rust packages, now honors “semantic
+versioning” when used in recursive mode.
+
+The [`guix refresh`
+command](https://guix.gnu.org/manual/en/html_node/Invoking-guix-refresh.html)
+now includes new “updaters”: `sourceforge`, for code hosted on
+SourceForge, and `generic-html` which, as the name implies, is a generic
+update that works by scanning package home pages.  This greatly improves
+`guix refresh` coverage.
+
+Packages and developers may also like the new [`--with-patch` package
+transformation
+option](https://guix.gnu.org/manual/en/html_node/Package-Transformation-Options.html),
+which provides a way to build a bunch of packages with a patch applied
+to one or several of them.
+
+  - ‘guix system image’
+  - GUIX_EXTENSIONS_PATH for GWL
+
+### Performance
+
+  - substitutes, discovery, ‘guix system init’
+  - channel-with-substitutes-available
+
+### POWER9 support, packages, services, and more!
+
+  - POWER9
+  - bug fixes



reply via email to

[Prev in Thread] Current Thread [Next in Thread]