Subject: Re: [bug#72452] [PATCH v5] gnu: Add guile-swayer.

From: Alec Barreto <[email-masked]>
Date: Sat, 14 Sep 2024 18:23:17 +0000

Nicolas Graves <[email-masked]> writes:

> If you want to pick a specific commit, you can do something like this
>
>   (let ((commit [commit])
>         (version "0.2.0")
>         (revision "0"))
>     (package
>       (name [name])
>       (version (git-version version revision commit))
>       (source (origin
>                 (method git-fetch)
>                 (uri (git-reference
>                        (url [url])
>                        (commit commit)))
>                 (file-name (git-file-name name version))
>                 (sha256
>                  (base32
>                   ""))))
>
>
> This makes it easier to upgrade to another given commit if necessary.

Thanks!
Funnily v0.3.0 was just released right after your message.
However it introduces a new (minor) issue.

There is a =manifest.scm= file in the project root which was for
building the program with guix since it wasn't (isn't) yet upstream. 
But now with the new 0.3.0 version the =guile-build-system= tries to
compile the =manifest.scm= as part of the program, causing build
failure.

The project itself could create a =make= file and the package definiton
could be switched to =gnu-build-system=.

Alternatively, since the manifest is arguably obsolete if this package
becomes upstreamed, the manifest can simply be removed.

We can wait for one of those situations, or just package it now in the
manner you suggested and pin the commit to where the package builds
(but still updating to  v0.3.0?)

Best,
Alec