[Slackbuilds-users] Build in search of a home

[J]

Eugen,
  

  
  

 If kitty isn’t using any go 1.20 features, generally you could safely downgrade the go.mod requirement. I’ve had to do this with a package I maintain, changing it back to go 1.19 on 15.0. As for go1.20 itself, I’ve not been able to get that going on 15.0. Generally when someone is building against go for dev, they are using the latest release, but we seem stuck on 1.19 for now (1.20 does build on -current) so long-term I don’t have a solution for that myself.   
  

  
I’ve been doing a “go mod vendor” and tarballing that, uploading to my server and linking the SlackBuild with the project source and my tarball to build so the entire build is “offline” once deps are downloaded. If you’re interested in an example, look up any nwg-* package on sbo.   
  

  
Wish you luck with kitty!
  

  
  
  
— Jay Lanagan
  
  
  

  
  
>   
> On Jul 17, 2023 at 4:07 PM,  <Eugen Wissner (mailto:belka at caraus.de)>  wrote:
>   
>   
>   
>  I looked into the build script and what is required for the next update and I think I can manage it. kitty requires Go 1.20, so it would be nice if google-go-lang could be updated to 1.20. As far as I understand google-go-lang 1.20 cannot be built with gccgo anymore and requires compiler bootstrapping. In the meanwhile I will probably use a binary compiler release. Go seems to have a so called vendoring feature, where you can pre-download the dependencies, put them into a tarball and build the thing offline. Worked for me in my first test. On Sat, Jul 15, 2023 at 01:42:54AM -0400, B. Watson wrote:  >   >  Does anyone here use kitty, and want to take over maintenance of it?  >   >  I've just updated kitty-bin to the latest release, but the  >  build-from-source kitty build is still at 0.26.5. I'm unlikely to ever  >  update it, because google-go-lang is just too much of a moving target  >  for me to want to aim at... and because kitty-bin works OK anyway.  >   >  Furthermore... I just don't like kitty much. I prefer rxvt-unicode,  >  or plain old xterm.  >   >  Any takers?  >  _______________________________________________  >  SlackBuilds-users mailing list  >  SlackBuilds-users at slackbuilds.org  >  https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users  >  Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/  >  FAQ - https://slackbuilds.org/faq/  >  _______________________________________________ SlackBuilds-users mailing list SlackBuilds-users at slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/  
>
>   
  
  
     
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20230717/ff33f311/attachment-0001.htm>