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

Consistency needed in release names and URLs #97

Open
surskitt opened this issue May 2, 2024 · 2 comments
Open

Consistency needed in release names and URLs #97

surskitt opened this issue May 2, 2024 · 2 comments

Comments

@surskitt
Copy link
Contributor

surskitt commented May 2, 2024

Hello,

I am trying to develop an asdf plugin to download and install launchpad versions. I've been having some problems with the consistency in the download urls starting with the 1.5 releases.

1.5.0/launchpad-linux-x64
1.5.1/launchpad-linux-x64
1.5.2/launchpad-linux-x64
v1.5.3/launchpad-linux-x64
v1.5.4/launchpad-linux-x64
v1.5.6/launchpad_linux_amd64_1.5.6

The urls have changed three times since 1.5, with the architecture either being x64 or amd64, the version either starting with a v or not and the filenames either using hypens or underscores. Add to this windows downloads either containing "windows" or "win".

Will there be some consistency in the release url names from now on? Could the current scheme be followed from now on?

Thanks.

@james-nesbitt
Copy link
Collaborator

Apologies for the mayhem. The current approach is considered the new standard (insert kxcd meme here.)

  • We are now adopting the v prefix for releases, as it is a golang standard - and allow for much easier imports;
  • We are now using goreleaser for the builds, and so we follow its standard, which is also the golang standard - hence the amd64 change.

@surskitt
Copy link
Contributor Author

OK, thanks for the clarification. I've written the plugin to handle the different version schemes for specific older versions and the newest scheme for all future versions, so it should be able to handle them all.

Thanks!

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

No branches or pull requests

2 participants