18:00:56 <jcajka> #startmeeting Go SIG meeting
18:00:56 <zodbot> Meeting started Mon Sep 13 18:00:56 2021 UTC.
18:00:56 <zodbot> This meeting is logged and archived in a public location.
18:00:56 <zodbot> The chair is jcajka. Information about MeetBot at http://wiki.debian.org/MeetBot.
18:00:56 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
18:00:56 <zodbot> The meeting name has been set to 'go_sig_meeting'
18:01:02 <jcajka> #topic Roll Call
18:01:16 <jcajka> Welcome all to the Go SIG meeting
18:01:34 * mroche waves
18:02:03 <Eighth_Doctor> .hello ngompa
18:02:04 <zodbot> Eighth_Doctor: ngompa 'Neal Gompa' <ngompa13@gmail.com>
18:02:12 <jcajka> #chair Eighth_Doctor
18:02:12 <zodbot> Current chairs: Eighth_Doctor jcajka
18:03:30 <Eighth_Doctor> anyone else, or is that it?
18:03:49 <jcajka> I think that is it
18:03:54 * jcajka hopes is wrong
18:04:07 * jcajka hopes he is wrong...
18:04:48 <Eighth_Doctor> ...
18:04:54 <jcajka> There are no tagged issues for meeting.
18:05:12 <Eighth_Doctor> how is Go 1.17 going?
18:05:16 <Eighth_Doctor> and Go modules support?
18:05:19 <jcajka> So just open floor, I guess.
18:05:26 <jcajka> #topic Open Floor
18:06:07 <mroche> As mentioned earlier in the channel, 1.17 was never submitted for F35. Is it at all possible to do any kind of retroactive application?
18:06:19 <jcajka> alexsaezm afaik should be looking in to it, but I haven't heard much news
18:07:23 <jcajka> mroche: I'm afraid that not really, it usually hangs on rebuild of the whole Go package stack, so the new compiler propagates through out distribution and we are too late for it, maybe Eighth_Doctor will correct me
18:07:43 <Eighth_Doctor> we are too late
18:07:53 <Eighth_Doctor> I think it was deferred to F36 automatically
18:08:35 <jcajka> although the compiler can live in rawhide and bit non-trivially you should be able to use in in supported releases of Fedora
18:09:26 <jcajka> like "dnf install --releasever rawhide golang" but you need to keep it up to date manually and there might be other can of worms
18:09:42 <jcajka> but that doesn't help with the distribution packages
18:09:52 <Eighth_Doctor> yup
18:10:05 <mroche> Yeah, I cloned the rawhide source and updated it to 1.17.1 and I'm using that locally. But as you said that doesn't affect the distro.
18:10:50 <mroche> I take it this would be a bad idea, but part of me wonders if golang would work within Modularity for the two latest compiler versions (or whatever Google declares support for).
18:11:12 <mroche> I don't have background in the Fedora golang stack, however.
18:12:40 <jcajka> mroche: modularity doesn't support parallel installs and IMNHO cause more headaches on both user and packager side than the upmentioned dnf command
18:13:48 <Eighth_Doctor> if we wanted parallel installs, we'd probably need to adopt something similar to the SUSE style for the Go compiler packaging
18:14:00 <jcajka> at least for me switching compiler version around is more common, though I'm definitively not common use case :)
18:14:09 <Eighth_Doctor> or like how Python does it in Fedora
18:15:18 <jcajka> yeah, but modules might make sense for creating multiple versions of fedora based golang compiler container or something analogous
18:15:47 <jcajka> not sure that it would scale to the whole packaging stack, at least not in current state of automation, I guess
18:16:14 * jcajka needs to check Go in SUSE again
18:18:05 <mroche> For Modularity I'd only be targeting specifically the packages provided by the `golang` package; I still need to learn more about how the -devel and other packages use the golang-provided ones beyond just the static compilation.
18:18:46 <mroche> * of programs. (didn't complete my thought, there)
18:19:23 <mroche> So this was a more naive thought discussion
18:21:45 <jcajka> mroche: I don't think anyone really uses Go beyond the static(from Go side)build, I think that modules shouldn't be that much different than normal package from this side
18:22:11 <jcajka> but it is really long time that I have checked or touched modularity
18:24:55 <jcajka> just one note, there has been some ask about possibility to not automagically add go macros BR via gometa, but I'm really afraid to touch any part of the macro stack to look in to it and this seems to me as rather fundamental change
18:31:10 <jcajka> any more topics?
18:33:37 <jcajka> I guess last call
18:33:42 <mroche> Nothing from me
18:35:21 <jcajka> #endmeeting