msys2.cmd wrapper is placed in `RUNNER_TEMP/setup-msys64` even for custom `location`

Open Beginner friendly
#673 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
66/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
github-actions, javascript
Domain
ci-cd, devops

Research direction

Read the action code that chooses the location path and creates the msys2.cmd wrapper, along with the discussion in issue #173. Check how a custom location affects the wrapper destination and how the default path is used. Done means a custom location keeps the wrapper from overwriting the caller's copy while the default setup still works.

Written by the indexing model from the issue text.

Description

I am working on a composite action that uses MSYS2. In order to not interfere with the calling workflow/action and its (potential) MSYS2 installation, I have set the location option to a custom value. The msys2.cmd wrapper however is still placed in same default location (RUNNER_TEMP/setup-msys64) which would overwrite the calling workflow/action's copy.

Is there a reason why the wrapper script isn't placed under the same location path? There doesn't appear to be any discussion of this in #173.

Dominant language
JavaScript
Stars
389
Forks
54
Avg merge
2d 7h
Merged PRs (30d)
8

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from msys2/setup-msys2

All issues in msys2/setup-msys2

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.