Skip to content

Conversation

@CrystalSplitter
Copy link
Collaborator

This adds:

  1. More Nix fhs utilities to get linux packaging working
  2. New packages for
    i. debian
    ii. tarball
  3. Updates to the package description, maintainers, naming

Note that because we're now packaging a .deb, we MUST provide an author with a contact email address. I've put my own down for now, as I'm the most consistent contributor for maintenance, but I'd ideally have it not be me.

We need these libs in the FHS Shell so Nix users
can actually build the linux packages needed.
This sets up debian and tarball packaging, adds
project maintainers and contact info (please
consider them placeholders!), and add new
targets for linux packaging.

We unfortunately MUST put down an author with
an email, so I'm putting myself down. That being
said, I'd really like this to change.
@nubesurrealista
Copy link
Collaborator

Looks good, I don't have any experience with packaging, I usually just compile common binaries. But I can actively test the Debian package because I currently use a Debian-based distro, so I can help with that, testing the package.

@nubesurrealista
Copy link
Collaborator

As part of the team and an active Debian user, I suppose I should be responsible for testing that the .deb package is fine and works, not necessarily meaning that I should be the maintainer or author in the description, but at least testing and making sure that it always works correctly n.n So count me in whenever you want to know if the Debian package is working properly and so on.

Copy link
Collaborator

@nubesurrealista nubesurrealista left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have a question. I would like to maintain compatibility with Debian 12, since, well, I'm still there. Debian 12 still has another year of support, so I don't think it should be abandoned when distributing software.

I mean, because the workflow uses Ubuntu latest, the binaries compiled in Ubuntu latest are not compatible with the glibc version of Debian 12, which would mean that any user on Debian 12 or based distros would not be able to use our software. Although I don't know if that's the case here, my personal workflow compiles an appimage on Ubuntu latest and I can use it, so I don't know if that principle applies here.

@CrystalSplitter
Copy link
Collaborator Author

CrystalSplitter commented Nov 23, 2025

It's ready to test right now! Would love it if you try. It should work with Debian 12, I would expect, but if not, we should use a debian builder. That can be added if it doesn't work.

Have you built a deb package yet with npm run package-deb and checked that works?

@CrystalSplitter
Copy link
Collaborator Author

Also for the record, this does not yet handle releases. That's done in #83.

Copy link
Collaborator

@nubesurrealista nubesurrealista left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok, I can confirm that building on ubuntu latest is not a problem for debian 12, the package is compatible. Sorry for the confusion haha, there is software that doesn't work in debian 12 when you compile it in ubuntu latest and I thought it was the general rule

@CrystalSplitter
Copy link
Collaborator Author

Awesome! That's great to hear. I would be surprised if it didn't work as Electron/Chromium I think ships with many of its own libc functions, and we don't build Electron when we run npm here.

@CrystalSplitter CrystalSplitter merged commit ecf63fb into master Nov 23, 2025
4 checks passed
@CrystalSplitter CrystalSplitter deleted the deb-packaging branch November 23, 2025 03:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants