Hi all! Long time no see!
I was wondering if there is a way to obtain the pijul sources without pijul? Like from github or sourcehut you can fetch tarballs over http, and i think a similar mechanism might be useful for the nest.
I’m not aware of any prior discussions around this, so thought I’d start this one.
Hi! welcome back. You can obtain them from Cargo. Since you need Rust to compile it anyway, you’re likely to have Cargo installed. If not, the tarballs are still accessible (I used to know the links from memory when I was actively involved in the ancestor of crate2nix, but I don’t anymore).
That’s fine for pijul itself, but what about other repositories on the Nest?
Thanks @joyously I think that’s a good clarification of what I meant by my question.
My thinking was that I would expect to have a way to obtain the sources of a given repository on nest.pijul.org without necessarily having pijul installed.
I’ll come clean on my intentions here (instead of X-Y probleming you): I’m trying to create an ebuild to allow installing Pijul via Gentoo’s package manager (built from source!). Broadly, the approach for Rust packages is to list all the dependencies, have Portage (the package manager) download them all (from crates.io) and put them in a “local” registry so the actual compilation/installation can proceed offline.
The approach I’ve been trying out is to then also list pijul itself in the dependency list, then copy that source folder into the work folder and proceed from there.
All that being said, I would like for the nest to have an “archive” fetching function that simply puts together a tarball of the source at a given point (channel?) or tag. Like github, gitlab, sourcehut and so many other source forges. Would that be a feature to consider for the Nest?
Just edited the title to clarify what I was really looking for…