Question: pkgr on new mac

[kylebaron]

Will the macos binaries run on macbook with M1 chip? If not, is there a way to get it installed on this arch?

[kyleam]

I think we'll need to update cmd/pkgr/goreleaser.yml to include arm64 or use macOS universal binaries (sounds like the second approach pretty much doubles the binary size):

pkgr/cmd/pkgr/goreleaser.yml

Lines 37 to 48 in 273972e

	build:
	binary: pkgr
	env:
	- CGO_ENABLED=0
	ldflags:
	- -s -w -extldflags "-static" -X 'github.com/metrumresearchgroup/pkgr/cmd.VERSION={{ .Env.VERSION }}'
	goos:
	- windows
	- darwin
	- linux
	goarch:
	- amd64

(edit: go 1.16 is required too, I think, but a new enough go version will already come in with drone's pull of goreleaser/goreleaser:latest)

[kylebaron]

Thanks, @kyleam ; that's helpful.

[dpastoor]

unfortunately, I am not certain that will be the fix you're hoping for. Eg you could already run pkgr "fine" under emulation (though there is no reason not to kick out an ARM binary. Plenty of stuff does - RStudio runs as x86, so does quarto (as underlying deno doesn't have a native arm build).

The bigger issue(s) will be two fold:

• teaching pkgr to understand the new CRAN format for arm-built binaries. I don't think it'll necessarily be that much work, it could be just some conditional logic in the paths that derive what URL(s) to reach out to.
• (for those doing local development) - I had mentioned this as an impending investigation to marc and joydeep last year that this will also have a knock on effect to MPN, if you want to continue to provide the consistent experience across platforms. At the time the prioritization was low as CRAN was just starting to even push out ARM binaries (and I didn't have access to an m1 to even test building with metrum's use of m1's being low). I'd suggest along with @seth127 for FYI to revisit if that holistic connection should be maintained.

[kyleam]

@dpastoor

The bigger issue(s) [...]

Ah, thanks for providing the broader, more relevant answer.

[kylebaron]

I didn't / couldn't follow the technical details on this. Is it possible to somehow use pkgr on m1 right now? Or would that require arm65 build?

For binary package question: is that something we can kick down the road and just work with source (we do it that way on Metworx anyway) or does something need to be solved on that front before we can go there?

Wondering about this as we're at a bit of a roadblock right now and looking for a way through.

KTB

[kyleam]

As I understand it, which may be wrong:

Is it possible to somehow use pkgr on m1 right now?

Yes, you can do it through Rosetta.

is that something we can kick down the road and just work with source (we do it that way on Metworx anyway)

Yes, you can build from source, though you run into the pain of needing to have the system requirements installed. (For Linux, they're not bundled, as they are for macOS and Windows, so using binaries speeds things up, but it doesn't free you from needing the system reqs.)