From a packaging perspective, Void Linux’s policy is to only get specific versions, ideally from a tarball download (for caching and checksumming purposes). Is there a backlight-auto-0.0.1.tar.gz somewhere I can download?
For build infrastructure, stuff works nicest when we can download an artifact (of source code) and go “This is $X package at $Y version.” This is of course source code so we can build from source, but it’s way nicer and lower maintenance (on the packaging side) than trying to wrangle a git repo, installing git on the builders, etc.
A low effort to achieve this on the software maintainer side is a github or gitlab repo, and you tag a version tag like v0.0.1. The forge then generates a download link like https://github.com/keybase/client/archive/v${version}.tar.gz providing a cachable artifact without doing any repository management. [Downside: github sometimes changes their automatic tarball generation technique, invalidating existing checksums for no apparent reason]
Yep! That’s probably even better ;) but does require a commitment to keeping that tarball around. Or, if your git tool can generate tarballs for tags, and does so repeatably (so the checksums are the same every fetch), this can ease server maintenance hassles.
In the future this’ll change, but I just don’t have the time right now. :) In any case I’ll try to remember to ping you or you’ll see the failure on your end and you can ping me
I love the simple and straightforward nature of the tool and its presentation. Even though it requires a bit of legwork, it’s very transparent and I have enough understanding and information to adapt it to my use case. Thanks for this!
Hey, is there a place I can download a versioned tarball of the software?
The zip contains the git repo, so you can checkout any version you want.
Or did you mean provide a binary? I have no intentions on providing binaries.
From a packaging perspective, Void Linux’s policy is to only get specific versions, ideally from a tarball download (for caching and checksumming purposes). Is there a backlight-auto-0.0.1.tar.gz somewhere I can download?
Isn’t it best to clone a repo or download the source and host, instead of pulling from sources which may not be online in the future?
Is it enough to host the git repo on len.falken.directory? Then once again, you can download any version…
Ultimately I can host that file but there’s no promises of it existing forever.
For build infrastructure, stuff works nicest when we can download an artifact (of source code) and go “This is $X package at $Y version.” This is of course source code so we can build from source, but it’s way nicer and lower maintenance (on the packaging side) than trying to wrangle a git repo, installing git on the builders, etc.
A low effort to achieve this on the software maintainer side is a github or gitlab repo, and you tag a version tag like
v0.0.1. The forge then generates a download link likehttps://github.com/keybase/client/archive/v${version}.tar.gzproviding a cachable artifact without doing any repository management. [Downside: github sometimes changes their automatic tarball generation technique, invalidating existing checksums for no apparent reason]I can for sure provide a tag in a git repo, I just don’t want to use github or gitlab :)
Will your forge or git tool provide a URL with a tarball?
this versioned source tarball can also be hosted from a static webserver, like it’s 1999.
Yep! That’s probably even better ;) but does require a commitment to keeping that tarball around. Or, if your git tool can generate tarballs for tags, and does so repeatably (so the checksums are the same every fetch), this can ease server maintenance hassles.
I’ve given in for now and will host it from GitHub https://github.com/lf94/backlight-auto/archive/refs/tags/0.0.1.tar.gz
In the future this’ll change, but I just don’t have the time right now. :) In any case I’ll try to remember to ping you or you’ll see the failure on your end and you can ping me
Thanks! Turns out Void doesn’t yet have Zig 0.11 or it’d be packaged already :)
I’m excited for Zig to break its LLVM dependency so we can update zig without bringing all of LLVM along.
Might be a good chance Zig 0.10 works, I haven’t tried.
I enjoy Zig, I might take a shot at crafting a build.zig for 0.10 and seeing what breaks from there
I love the simple and straightforward nature of the tool and its presentation. Even though it requires a bit of legwork, it’s very transparent and I have enough understanding and information to adapt it to my use case. Thanks for this!