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

Fix/lega commander installation and readme #321

Merged
merged 14 commits into from
Jan 10, 2025

Conversation

pavelvazquez
Copy link
Contributor

Updated Install Script:

  • Adjusted the GITHUB_DOWNLOAD logic to use the correct repository (ELIXIR-NO/FEGA-Norway).

  • Changed handling of TAG and VERSION logic to support the monorepo structure.

  • Removed Deprecated Adjustments: Removed unused adjust_os and adjust_arch functions following GoReleaser deprecations.

  • Improved Logging: Enhanced log messages to provide clearer status updates during installation (e.g., success, failure).
    Windows Compatibility:

  • Improved defaults: BINDIR defaults to /usr/local/bin or user-provided path.

  • Confirmed instalation for Linux and Mac

Updated installation instructions in README.md and removed old badges

@kjellp kjellp force-pushed the fix/lega-commander-install branch from d981a21 to 50cbd9a Compare January 8, 2025 08:37
@kjellp
Copy link
Contributor

kjellp commented Jan 8, 2025

I tested the install script on Linux now, and ran into errors:
image

I downdloaded the install.script manually from the branch in the repo, and executed it locally with the -b option to install it in a custom location not requiring sudo.

There is a 404 error in there related to fetching the Linux_x86_64 tar.gz file. @Parisa68 is it this specific version of the release file that only will be generated upon the PR merge?

@pavelvazquez
Copy link
Contributor Author

The install script searches into the release with the latest tag. Crypt4gh is having the latest tag, so it is trying to download it. It fails because the url is wrong. Do we need that the Crypt4gh also has the latest tag?

@Parisa68
Copy link
Contributor

Parisa68 commented Jan 8, 2025

we can try to keep lega-commander-assets "latest"(the solution should be tested), but is that what we want or we want to change the script to work specifically for lega commander?

@kjellp
Copy link
Contributor

kjellp commented Jan 8, 2025 via email

Copy link
Contributor

@kjellp kjellp left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tested on linux and works correctly now (not tested custom tag feature)

@pavelvazquez pavelvazquez merged commit ad814b2 into main Jan 10, 2025
1 check passed
@pavelvazquez pavelvazquez deleted the fix/lega-commander-install branch January 10, 2025 14:30
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

Successfully merging this pull request may close these issues.

3 participants