Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Request] Provide non-generic packaging CI for major linux distributions #225

Open
mardab opened this issue Jun 3, 2024 · 3 comments

Comments

@mardab
Copy link

mardab commented Jun 3, 2024

I have tried reproducing build on a "real" Ubuntu 22.04 according to provided docmentation, then adjusting for errors which arose, then repeated the same with provided Dockerfiles.

In all 4 cases builds fail, and while generic release works, I do believe CI for .deb/.rpm package would to wonders do popularization and reproducibility of the builds.

Aside from the fact that as of writing this packages Ubuntu 22.04's universe are a bit long in the tooth for current builds, such improved CI could be more easily extended into providing packages for more demanding systems, such as Flatpak, AppImage, various cloud-oriented formats or Snap'd.

@mardab mardab changed the title [Request] Provide non-generic packaging CI for major linux distributions [Feature Request] Provide non-generic packaging CI for major linux distributions Jun 3, 2024
@mhx
Copy link
Owner

mhx commented Jun 3, 2024

Thanks for your feedback!

I'm not quite sure I understand the core of the issue here, though.

In all 4 cases builds fail,

Can you be more specific about what failures you're seeing?

and while generic release works,

I'm assuming you're referring to the statically linked binary release?

Aside from the fact that as of writing this packages Ubuntu 22.04's universe are a bit long in the tooth for current builds,

Not sure what you mean. The 22.04 Dockerfile exists just to ensure this still builds with 22.04. The regular Dockerfile is based on 24.04, and this is also what's being used for the release builds.

Are you suggesting that the CI should produce deb/rpm/... package artifacts?

@mardab
Copy link
Author

mardab commented Jun 10, 2024

Yes, that is exactly what I'm suggesting, with all package artifacts buildable from single container at a bit higher upfront engineering cost and recent calls throughout community to have packages (mostly with Flatpak) be maintained by original author/maintainer, having even the basic packages setup would allow for much easier adoption by people who won't realize that current build documentation might be outdated.

I cannot confirm that one yet, but based that assumption on differences between what's in readme and all those Dockerfiles that pushed me to find actual problems with my setup, which is why I cannot confirm at the time of writing this and until I fix these issues, thank you for leading me onto that discovery.

@mhx
Copy link
Owner

mhx commented Oct 19, 2024

[...] recent calls throughout community to have packages (mostly with Flatpak) be maintained by original author/maintainer [...]

Source? Which community exactly?

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

No branches or pull requests

2 participants