4 ms·
from this post: > Don’t ship pre-built binaries [...] Once you ship your [source] tarballs, your job is done. It’s the users who will go to their distro and as
by theamk 5y ago
from this post:
> Don’t ship pre-built binaries [...] Once you ship your [source] tarballs, your job is done. It’s the users who will go to their distro and ask for a new package.
from author's own Sourcehut's project page [0]
# Add the following line to /etc/apt/sources.list
deb https://mirror.sr.ht/debian sid main
# Install signing key
wget -q https://mirror.sr.ht/debian/key.asc -O - | sudo apt-key --keyring /etc/apt/trusted.gpg.d/debian.sr.ht.gpg add -
sure doesn't look like "shipping the tarball" to me :)
[0] https://man.sr.ht/packages.md https://man.sr.ht/packages.md
- ddevault 5y agoSourceHut maintains actual package repositories based on standard package managers, most of which are overseen by independent contributors. The Debian packages are maintained by Denis Laxalde, who is a volunteer with no relationship to SourceHut. This approach enjoys most of the same benefits as using upstream packages does - contrast this with, for example, shipping a bunch of Docker images. SourceHut is under heavy development and shipping multiple releases per day during busy weeks, and the workload of keeping up with it downstream is quite large. NixOS is working on it, but few other distros are brave enough to try. Once we ship 1.0 then it will make a lot more sense for distros to start maintaining their own packages for it, and their job will be made easier given that they can start by copy/pasting the interim package manifests maintained by these SourceHut-specific teams. On the whole I would argue that I'm walking the walk here.