You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I see that OBS has been setup now to build debian / ubuntu packages automatically.
Can the same setup be extended to build the portable linux images?
If it's possible, I would be happy to help write scripts, etc.
If the same setup can't be extended, I would appreciate any tips on starting a new setup for this. (I am familiar with Travis CI, Gitlab CI, Github Actions, but never tried OBS yet).
The text was updated successfully, but these errors were encountered:
Having an official portable build to take and repackage in other distros would be nice. It would really help to spread this project. There's at least one distro considering this. Taking the unofficial binaries seems not like something a distro can do as you need to trust more and completely unknown users than just @Eloston.
Building chromium is a task only major distributions can tackle. Adding ungoogled-chromium-portablelinux to OBS would be perfect. It just needs to stay portable (which means /opt, obviously).
I came to understand that the OBS is operated by @braewoods and @jstkdng. Since Eloston obviously approves this, that would be trustworthy enough, I think.
It would be most beneficial if musl libc version of portable build was built along with glibc. Currently for Alpine Linux this is the only way besides compiling from source to run Ungoogled Chromium, and any non-surveilance browser for that matter.
Hi @braewoods @Eloston @wchen342
I see that OBS has been setup now to build debian / ubuntu packages automatically.
Can the same setup be extended to build the portable linux images?
If it's possible, I would be happy to help write scripts, etc.
If the same setup can't be extended, I would appreciate any tips on starting a new setup for this. (I am familiar with Travis CI, Gitlab CI, Github Actions, but never tried OBS yet).
The text was updated successfully, but these errors were encountered: