Hello, I'm in the process of releasing guile-config 0.5, which unfortunately is backward incompatible in some ways.
As a result I want to give developers who are using it a chance to upgrade gradually. To this end, in the attached patch, I add a new variable for 0.5. My intention is to have 0.4.2 and 0.5 coexist for a while and then to switch fully to 0.5 in due course. Is this an acceptable way of doing a gradual transition to a backwards incompatible version of the library? Best wishes, Alex
From fadba5c1c27d96b8e49dcf987eb3c09a2bbb0776 Mon Sep 17 00:00:00 2001 From: Alex Sassmannshausen <a...@komputilo.eu> Date: Wed, 17 Feb 2021 16:48:39 +0100 Subject: [PATCH] gnu: Add guile-config-0.5. * gnu/packages/guile-xyz.scm (guile-config-0.5): New variable. --- gnu/packages/guile-xyz.scm | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/gnu/packages/guile-xyz.scm b/gnu/packages/guile-xyz.scm index 984c2b1109..b62dbe20d5 100644 --- a/gnu/packages/guile-xyz.scm +++ b/gnu/packages/guile-xyz.scm @@ -1582,6 +1582,21 @@ above command-line parameters.") (define-public guile3.0-config (deprecated-package "guile3.0-config" guile-config)) +(define-public guile-config-0.5 + (package + (inherit guile-config) + (name "guile-config-0.5") + (version "0.5.0") + (source + (origin + (method git-fetch) + (uri (git-reference + (url "https://gitlab.com/a-sassmannshausen/guile-config";) + (commit version))) + (file-name (git-file-name name version)) + (sha256 (base32 + "1xrl8bdcvvvbsrms0s3pp3d698541fv5b5kyy1z2kwli7akvdiph")))))) + (define-public guile-hall (package (name "guile-hall") -- 2.28.0
signature.asc
Description: PGP signature
