platform support megaticket

[mxcl]

• Windows (started: v1 wip libpkgx#48)
• iOS Jailbreak (discussion Future support: (jailbroken) iOS? #182)
• Android
• Umbrel
• i686 32 bit (attempting to run pkgx on iShell i686 32-bit architecture on iOS #886)

Maybe

• WSL1 (discussion WSL1 #493)

Architectures

What do we need? Let us know.

Supported

• macOS >= 11
  • aarch64
  • x86-64
• Linux (glibc >= 2.28)
  • aarch64
  • x86-64
• WSL2
  • x86-64

[burdiyan]

Having native Windows support would be massive! Can't wait.

[felipecrs]

Deno supports Ubuntu 16.04, but Tea does not (because of the old version of glibc).

I'm just wondering... would it be too hard to add support for older versions of GLIBC?

[jhheider]

I'm just wondering... would it be too hard to add support for older versions of GLIBC?

Yes, extremely. ;)

If you're interested, I've been working on getting a build of glibc we can inject for tea binaries on pkgxdev/pantry#147. glibc is a tricky beast, since it's all the way at the bottom of the stack. If you have insights or assistance to offer, it's always greatly appreciated.

(I won't badger you to move to an LTS that's still in standard support, even though 16.04 is over 7 years old. I want to, because it's easier for me, but I'm too nice to do it.)

It's entirely possible, of course, that you can build tea and many packages manually on 16.04. But our bottles are built against a debian buster GLIBC (2.28) and ubuntu 16.04 is 2.23, it looks like.

[felipecrs]

Alright, it's perfectly understandable.

My needs to use Ubuntu 16.04 are beyond me, thanks for understanding that. And I wanted to use Tea on Ubuntu 16.04 to make that less painful (e.g. I need to install Python 3.10 on Ubuntu 16.04).

If you're interested, I've been working on getting a build of glibc we can inject for tea binaries on pkgxdev/pantry#147. glibc is a tricky beast, since it's all the way at the bottom of the stack.

Nevertheless this sounds amazing. If someday it gets done, I suppose curl -fsS https://tea.xyz | sh could handle it as well (i.e. installing tea's glibc manually before invoking tea itself).

If you have insights or assistance to offer, it's always greatly appreciated.

Sorry but I have no assistance to offer at this point. I can just say that I think you are doing the right thing. :)

[jhheider]

Well, I appreciate the encouragement, except for the fact that working at the glibc level is utterly painful and I'd love to bin the whole idea. 😆

There are a non-zero number of people using Alpine or Amazon Linux 2 who also need this, so it should be figured out.

[jhheider]

i don't recall, per se. My gut says it's not tiny. probably in the 10-100MB range, if i were doing fermi approximation.

[felipecrs]

Sorry, for context I had asked:

Out of curiosity, do you know how big (MB) a bottle of glibc would look like?

But I deleted it from here and posted in pkgxdev/pantry#147 instead. Now that you asked, I deleted it from pkgxdev/pantry#147 too.

---

i don't recall, per se. My gut says it's not tiny. probably in the 10-100MB range, if i were doing fermi approximation.

That's not bad at all, I was just wondering since you mentioned Alpine users. lol

[Trung0246]

Is freebsd supported if compile from source?

[jhheider]

this is a fantastic question. in theory, supporting it should be trivial, since it uses most of the same low-level tools. patches would be needed to libpkgx and pkgx to recognize the platform, and there would probably be some changes needed to deal with libc differences. but if deno/rust work on freebsd (and i assume they do), a port isn't a big deal (until we get to building the entire pantry. that is a big deal. ;) )

if you get libpkgx/pkgx working, we'd love to support freebsd.

[mxcl]

Is freebsd supported if compile from source?

We would love to support freebsd.

Sadly, it is not currently trivial to boostrap the key packages required to build the rest.

1. install deno with the freebsd system package manager
2. clone pkgx
3. deno task install
4. pkgx integrate (required to easily use the pantry, sorry, will fix eventually)
5. clone the pantry
6. In the clone: dev
7. pkg edit llvm.org remove deps (install them from system)
8. pkg build llvm.org

then work from there.

what we need is some kind of “bootstrap pkgx for a new system” manual with helper scripts. Let me put that on my TODO list. We'll need it for Windows native anyway.

Once we have verified a new system can be supported we will put it into our CI/CD so that all packages are built and hosted on our infra.

[mxcl]

First steps for native Windows are almost complete, just got some npm build issues pkgxdev/libpkgx#48)

[burdiyan]

I recently learned about Pixi at https://prefix.dev (not affiliated, and I'm sorry to post a competitor here). It supports Windows and all the other platforms, and because they are based on Conda packages, they already have pretty good collection of existing packages.

Would be great for you guys to join forces, because the world would be a better place :)