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.

Sign up for GitHub

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

Jump to bottom

[Suggestion] Consider using the Github releases for the downloads page #2

Open
Nefari0uss opened this issue Dec 20, 2017 · 2 comments
Open

[Suggestion] Consider using the Github releases for the downloads page #2

Nefari0uss opened this issue Dec 20, 2017 · 2 comments

Comments

@Nefari0uss
Copy link

My suggestion is that the GitHub release page for the various ranger versions be used as links for the download page instead of putting a compressed copy of ranger in the repo. This has a nice benefit of keeping the repo small.
@hut
Copy link
Member

hut commented Dec 21, 2017

Then we would have no PGP-signed releases.

Maybe the tarballs that github produces are always reproducible, bit by bit, then I could sign those too.

@vifon
Copy link
Member

vifon commented Dec 21, 2017

We can create signed tags in Git, that should serve as a signed release. Even in a separate repository, just for the binary releases.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@hut @vifon @Nefari0uss