Replies: 2 comments 1 reply
-
any reason spotbugs can't set the executable bit in their tarball? I'm also open to adding an env var around this but it definitely seems like something that should be fixed upstream too |
Beta Was this translation helpful? Give feedback.
0 replies
-
I was able to temporary workaround this issue. But it is bad. Ideally this should go into aqua registry spec. Some yaml field to update permission for a file matching the pattern. Requiring the user of the tool to do it manually every time is bad UX. I realize that it might be hard to convince aquaproj to change the spec. "aqua:iilyak/spotbugs/spotbugs" = { version = '4.9.0', postinstall = """\
mise where aqua:cloudant/spotbugs/spotbugs | xargs -I {} chmod +x {}/spotbugs/bin/spotbugs
"""} |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I am trying to write an aqua registry.yaml for https://github.com/spotbugs/spotbugs. The release of spotbugs doesn't have an executable flag set. So I am trying to use the posthook to set it.
However the chmod command will fail because it runs in the current directory. I think the mise should pass
MISE_TOOL_DIR
(or some other suitably named) environment when it runs postinstall hook defined for the tool. TheMISE_TOOL_VERSION
would be nice as well.Beta Was this translation helpful? Give feedback.
All reactions