Code: https://github.com/pkgforge/soar
Soar is like linuxbrew (homebrew) but whose packages are 100% static & relocatable on any Linux Distro.
Code: https://github.com/pkgforge/soar
Soar is like linuxbrew (homebrew) but whose packages are 100% static & relocatable on any Linux Distro.
No. Though some of it can be inferred from the overtly verbose logs
No again.
Currently, most packages are built from
git HEAD
onalpine:edge
ordebian-unstable
build containers. So if the fix for this affected libwebp is shipped to the images that the build containers are based on (likely because we use edge/unstable images), then any affected packages would also automatically receive this fix.To store a complete dependency graph, we will most likely need some custom tooling because our build recipes differ wildly for each package. If you have any ideas, please open a discussion on the repo. Thanks!
Thanks for the reply.
How often do packages get rebuilt? Is it only when there’s a new version? The problem in that case would be that a package that is no longer developed (or has very long release cycles) would not receive the fix.
Yes, only if there’s a new version.
We specifically mark these kinds of packages as
outdated
(evendeprecated
) if they are older than 90 daysCurrently, the stats:
This will improve if we can get more builders, currently we use the free CI provided by github actions
Interesting, thanks!