aports

Thanks for providing an example of the search query you had problems with. Interestingly, I haven't noticed the decay in Google search quality that many are complaining about. The first hit when I use your Google query is https://github.com/alpinelinux/aports/blob/master/COMMITSTYL... which seems correct?

Distro repositories (like the one you have on Debian / Ubuntu / Redhat etc) do this. They work on a different model, where only packages that are deemed "worthy" are included, and there's a small-ish set of maintainers that are authorized to make changes and/or accept change requests from the community. In contrast, programming language package managers like cargo, pip or npm let anybody upload new packages with little to no prior verification, and place the responsibility of maintaining them solely on their author. The distribution way of doing things is sometimes necessary, as different distributions have different policies on what they allow in their repositories, might want to change compilation options or installation paths, backport bug and security fixes from newer project versions for compatibility, or even introduce small code ch

Thank you, Promising work! Question: How was zstd built in the tests? In other words, was the possibility of 2-stage pgo+lto optimization taken into account? (the alpine zstd claim ~ "+30% faster on x86_64 than the default makefile" [1] ) [1] "" # 2-stage pgo+lto build (non-bootstrap), standard meson usage. # note that with clang, # llvm-profdata merge --output=output/somefilename(?) output/.profraw # is needed. # believe it or not, this is +30% faster on x86_64 than the default makefile build (same params).. # maybe needs more testing # shellcheck disable=2046 ""* https://github.com/alpinelinux/aports/blob/master/main/zstd/...

Instead, currently, all packages become lint-unclean, all maintainers need to read up on what the new thing is, how it might break, whether/how it affects them, manually run some tests, and finally decide to opt in. This causes a lot of overhead and manually executed mechanical changes across packages. I always wondered if Debian/Ubuntu could benefit from a "monorepo". It seems to work for other distributions, e.g. Alpine Linux and Homebrew. https://github.com/alpinelinux/aports/tree/master/main Right now every Debian package lives in a separate repo, or it doesn't even have to live in a repo at all AFAIK. I think Debian has the most packages because their process is very loose and decoupled (as well as it being one of the oldest distros). But having tighter integration does help move things forward faster.

Since I follow alpine linux dev a bit, I thought this: https://github.com/alpinelinux/aports/blob/master/testing/ru... Is the port of rustc to run natively on AL? Bit outdated now but it seemed to work the last time I tried it. You'd have to enable the testing repo to use it however.

That is awesome! Congrats ncopa. Incidentally I ported go and then docker to Alpine Linux (musl and hardened toolchain fixes) almost 2 years ago: https://github.com/alpinelinux/aports/commit/abfdfd32d2c6818... https://github.com/alpinelinux/aports/commit/4248d1a88bcde1d...