104
Collabora and Valve have built and released a preview aarch64 port of Arch Linux (Holo Core) for the Steam Frame (www.collabora.com)
submitted 2 months ago by to c/linux_gaming@lemmy.world
13 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] 4 points 2 months ago (8 children)

It doesn't appear to rely on ALARM, does it? I haven't dug through the sources thoroughly yet, but I haven't see anything there that indicates they're using ALARM stuff.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 8 child comments
    •
  • [–] 3 points 2 months ago (7 children)

    Yeah, they jumped straight into reinventing the wheel for some reason. Alarm forums may be dead but the project and repos are still getting updates. Why spin your own shit?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 7 child comments
    •
  • [–] 11 points 2 months ago (5 children)

    What's there to reinvent? Upstream Linux software already builds for ARM.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 5 child comments
    •
  • [–] 2 points 2 months ago (4 children)

    Package repositories, recipes, and support paths

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 5 points 2 months ago (3 children)

    Package repositories, recipes, and support paths

    The existing stuff needs to be adapted, not reinvented. In my time as packaging some software for my own use under openSUSE I barely seen software that needed adaptions in the package spec file for other CPU architectures. Emulators were the most common exceptions I encountered and even that changed a lot since then thanks to upstreams porting those to Android and Apple M processors. Collabora lists as main challenges the ability to access the upstream source codes for reproducibility, not "repositories, recipes, and support paths".

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 2 points 2 months ago* (2 children)

    Man, if it was that simple, ALARM wouldn't exist and arch would have (at least) allowed aarch64 packages in the AUR years ago. There are other factors in play than what I listed above, but it's still weird to not even mention the existing community efforts.

    Reproducible builds are one step closer than what ALARM was already providing. It's cool, but it's still just one step up, and a rewrite. I don't understand why Collabora went in this direction aside from having more billable hours.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 2 points 2 months ago* (1 child)

    Man, if it was that simple, ALARM wouldn’t exist and arch would have (at least) allowed aarch64 packages in the AUR years ago.

    Arch's policy is to offer only x64 binaries. They don't offer ARM packages because they don't want to. ALARM exists because Arch does not want the contributions.

    While it's not zero work, your claim of reinventing the wheel overstates what compiling software that's already compatible with ARM requires.

    I'm reading what Collabora wrote and nowhere is that blog post did they state that compiling stuff for ARM and the packaging are the hard parts. They explicitly called out the reproducibility parts, not the rest.

    If your small community project with dead forums and broken logs (see below) can do it, a team of full time Linux engineers can do it in a relatively small amount of time, probably with logs.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •