Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Local package repository #93

Open
markusbkk opened this issue Nov 21, 2022 · 2 comments
Open

Local package repository #93

markusbkk opened this issue Nov 21, 2022 · 2 comments
Labels
question Further information is requested

Comments

@markusbkk
Copy link

Just curious. If I wanted to set up a local package repository with custom packages not in the official repo, how would I best go about setting this up?

@stapelberg
Copy link
Member

See distri help, specifically distri export, and possibly also distri mirror.

For installing a package, distri only needs the squashfs file itself (e.g. i3-amd64-4.18.1-12.squashfs) and the accompanying metadata file (i3-amd64-4.18.1-12.meta.textproto). Just make them available via HTTP, with any webserver you want. That’s all distri export does*.

For use-cases like debugfs, you also need a meta.binaryproto that combines the metadata of all packages. That’s what distri mirror produces. But if all you need is installing packages, you can skip this step.

[*] For performance, you can optionally serve the .squashfs files gzip-compressed (or zstd once #77 is done). distri export serves these files if you manually create them (e.g. using parallel gzip -9 --keep ::: *.squashfs), but if you use a different HTTP server you probably need to enable that explicitly.

@stapelberg stapelberg added the question Further information is requested label Nov 21, 2022
@markusbkk
Copy link
Author

See distri help, specifically distri export, and possibly also distri mirror.

For installing a package, distri only needs the squashfs file itself (e.g. i3-amd64-4.18.1-12.squashfs) and the accompanying metadata file (i3-amd64-4.18.1-12.meta.textproto). Just make them available via HTTP, with any webserver you want. That’s all distri export does*.

For use-cases like debugfs, you also need a meta.binaryproto that combines the metadata of all packages. That’s what distri mirror produces. But if all you need is installing packages, you can skip this step.

[*] For performance, you can optionally serve the .squashfs files gzip-compressed (or zstd once #77 is done). distri export serves these files if you manually create them (e.g. using parallel gzip -9 --keep ::: *.squashfs), but if you use a different HTTP server you probably need to enable that explicitly.

Awesome! Sounds fairly easy.

I assume I can create my own frontend too, by using distri-repobrowser as an example

Will try all of that tonight when I get back from my day job.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants