08:42:22 <jperkin> pjustice: yeh, sorry, the pkg_alternatives interface is horrendous - it was deliberately modelled on a similar tool in debian I believe, but I _always_ have to go to the manual page to figure out what I need to do
08:43:34 <jperkin> just check that there is an +ALTERNATIVES file in the pkgdb for each package you want to use, e.g. /opt/local/pkg/go122*/+ALTERNATIVES
08:45:07 <jperkin> also verify that you aren't installing the "go" meta-package, that will always pull in a specific version tied to whatever is the current default across the tree
08:47:55 <jperkin> I think "manual" is what you want: https://gist.github.com/jperkin/9bbb574b8418f67d8b291968cf00ba90
14:49:01 <pjustice> The go meta-package seems to point to 1.22, though.
14:49:22 <pjustice> But telling alternatives to `auto` results in 1.18.
14:57:25 <jperkin> yeh any meta-package like that and pkg_alternatives are fundamentally incompatible (which is why in the past I removed the 'ruby' meta-package, I should probably do the same with 'go')
15:00:41 <pjustice> So how do I tell alternatives to un-everything go and let the metapackage win?
15:01:37 <jperkin> oh, you _want_ to use the meta package..
15:02:21 <pjustice> Well, it seems to do a reasonable job of staying in the zone where most stuff works.
15:04:26 <jperkin> I'll need to do some testing, as I'm not sure it'll work reliably - whenever you upgrade the go packages I think the pkg_alternatives registration will re-run
15:04:40 <jperkin> it's why they're fundamentally incompatible
15:06:22 <pjustice> Ah, ok.  I'll just make my automation set it manually then.  And remove the meta-package.
15:06:26 <pjustice> Thanks!
15:07:09 <jperkin> ok, I think I'll go ahead and remove it to avoid future confusion
15:22:14 <jperkin> oh I'm mistaken, it's not like the ruby meta-package, it literally just depends on go, it doesn't provide its own wrappers
15:26:42 <jperkin> so you should be able to continue using it, but there's no way for pkg_alternatives to know which one you want based simply on installing 'go', so if you have multiple go* installed then you'll still need to 'pkg_alternatives manual go<x>' to explicitly select a version
16:19:30 <pjustice> Without the meta-package, and with multiple installed go1xx, what will be / is there a default?
16:21:24 <jperkin> I think it'll default to whatever version you installed first
16:21:44 <pjustice> Thanks
16:21:45 <jperkin> after that it should respect any override