On Wed, Jan 11, 2023 at 08:02:15PM -0500, Leo Famulari wrote:
> That's correct. You can put something like this in the package
> arguments:
>
> #:go ,go-1.19
This was undocumented... sorry! I just rectified that in commit
9ec62d1b9c55104f9ab81b95d82988c627a23415.
On Wed, Jan 11, 2023 at 05:25:18PM +, ( wrote:
> Pretty sure there *is* already a #:go argument, but I might be misremembering.
That's correct. You can put something like this in the package
arguments:
#:go ,go-1.19
> Pretty sure there is already a #:go argument, but I might be misremembering.
Just took a look in the build-system and I can't find that argument.
Maybe I didn't search correctly anyway... :)
Cheers!
On Wed Jan 11, 2023 at 1:49 AM GMT, Hilton Chain wrote:
> Though it's possible to package the last version supports Go 1.17 (v1.38.0),
> I wonder if we can
> adjust the build system so that a Go package could be specified via an
> argument in the package
> definition.
Pretty sure there *is*
Hilton Chain writes:
> Hi Guix,
>
> I'm trying to package wakatime-cli[1], while Guix uses Go 1.17 as the
> default, the package requires Go 1.19 at the current version
> (v1.60.4).
>
> Though it's possible to package the last version supports Go 1.17
> (v1.38.0), I wonder if we can adjust the
Hi,
> Hi Guix,
>
> I'm trying to package wakatime-cli[1], while Guix uses Go 1.17 as the
> default, the package requires
> Go 1.19 at the current version (v1.60.4).
>
> Though it's possible to package the last version supports Go 1.17 (v1.38.0),
> I wonder if we can
> adjust the build system so
Hi Guix,
I'm trying to package wakatime-cli[1], while Guix uses Go 1.17 as the default,
the package requires
Go 1.19 at the current version (v1.60.4).
Though it's possible to package the last version supports Go 1.17 (v1.38.0), I
wonder if we can
adjust the build system so that a Go package
