go-sig-meeting
LOGS
<@alexsaezm:fedora.im>
18:00:08
!startmeeting Go SIG meeting
<@meetbot:fedora.im>
18:00:09
Meeting started at 2026-06-29 18:00:08 UTC
<@meetbot:fedora.im>
18:00:09
The Meeting name is 'Go SIG meeting'
<@alexsaezm:fedora.im>
18:00:14
!topic Roll Call
<@alexsaezm:fedora.im>
18:00:19
Hi everyone! As always we'll wait ~5 minutes for everyone to join.
<@buckaroogeek:fedora.im>
18:00:40
!hello
<@zodbot:fedora.im>
18:00:42
Brad Smith: Brad Smith (buckaroogeek)
<@alexsaezm:fedora.im>
18:00:49
o/
<@alexsaezm:fedora.im>
18:05:34
Well, looks like it you Brad and me 🙂
<@buckaroogeek:fedora.im>
18:05:57
Yes indeed
<@buckaroogeek:fedora.im>
18:06:44
For once I am actually working on a small go utility - tests install of kubernetes locally on one or more VMs.
<@alexsaezm:fedora.im>
18:07:29
Oh, are you going to use it for testing something in Fedora? Or is not related?
<@buckaroogeek:fedora.im>
18:08:05
When I build a new release of kubernetes to fedora, i like to test install just to make sure I did not break anything
<@alexsaezm:fedora.im>
18:08:25
makes sense
<@buckaroogeek:fedora.im>
18:08:33
so i did not use it for kubernetes1.36 and there is a problem :)
<@buckaroogeek:fedora.im>
18:08:46
bad me
<@alexsaezm:fedora.im>
18:09:23
happens to the smartest ones 😄
<@buckaroogeek:fedora.im>
18:10:01
also i finshed a rust package last week - sure glad go is using vendored packages
<@alexsaezm:fedora.im>
18:11:33
I have no clue how they handle dependencies tbh
<@buckaroogeek:fedora.im>
18:12:01
like go used to be in fedora - painful
<@buckaroogeek:fedora.im>
18:12:06
in my opinion
<@alexsaezm:fedora.im>
18:12:44
I guess they will consider a similar solution at some point.
<@alexsaezm:fedora.im>
18:13:42
btw... talking about building stuff... I see you have a ticket in the go/sig tracker tagged as meeting related to CGO_CFLAGS
<@alexsaezm:fedora.im>
18:13:54
https://forge.fedoraproject.org/go/sig/issues/67
<@buckaroogeek:fedora.im>
18:14:00
A vendored option is available but not encouraged
<@buckaroogeek:fedora.im>
18:14:12
yes
<@buckaroogeek:fedora.im>
18:16:01
I was thinking that these should have default values consistent with fedora standards
<@buckaroogeek:fedora.im>
18:16:48
but maybe that is just a packager centric position :)
<@alexsaezm:fedora.im>
18:20:54
I recall setting some of these things in CentOS/RHEL while ago but I don't recall exactly where they are set right now, I will check them later. I think we can find a good default settings for them and packages can always change them later if they need them. Is this based on something you saw?
<@buckaroogeek:fedora.im>
18:22:33
One of the packages I was working on needed them set to build correctly so I was wondering why they did not have defaults
<@alexsaezm:fedora.im>
18:23:33
I will check it and go back to you with what I find
<@alexsaezm:fedora.im>
18:23:51
I recall a conversation about this recently but I can't find it in my notes (which is the normal thing for me)
<@buckaroogeek:fedora.im>
18:24:02
sounds good
<@alexsaezm:fedora.im>
18:25:20
I don't see any other issue tagged. Is there anything you want to talk about (we can talk about the tool you are making outside the room, I'm interested :D)
<@buckaroogeek:fedora.im>
18:25:44
Nothing else from my end
<@alexsaezm:fedora.im>
18:26:31
Ok. Just for the record (I already notified this on the Fedora Golang room but just in case someone checks the logs later): I did a mass prebuild of 1.27rc1 and the results are here:
<@alexsaezm:fedora.im>
18:26:39
<@alexsaezm:fedora.im>
18:27:02
And that's it from my end too
<@buckaroogeek:fedora.im>
18:27:09
thanks!
<@alexsaezm:fedora.im>
18:27:25
We can call it then
<@alexsaezm:fedora.im>
18:28:46
Thanks for joining!
<@alexsaezm:fedora.im>
18:28:51
!endmeeting