Re: policy proposal: updating packages with many dependencies

[Benny Siegert <bsiegert%gmail.com@localhost>]

On Wed, Mar 19, 2025 at 9:38 AM Thomas Klausner <wiz%netbsd.org@localhost> wrote:
> >  > - go
> >
> > Isn't every new go version a new package, so the concern is not about
> > committing that package but about bumping the default vesrion?
>
> Yes, you're right. Let's remove go from this list - it's a separate,
> similar discussion for updating the default version of packages like
> Go, Python, and PHP, which we can have another time.

I see point updates of Go as unlikely to break anything. The part
where a bulk build is needed is when you change the default version,
as you mentioned. I do this with bulk-test-go and try to proactively
fix any fallout _before_ flipping the default.

Whether that happens in a branch or not is not that relevant, since
the change of default version is a one-line change that is easy to
make even in a pending commit.

-- 
Benny