Skip to content

Conversation

@N-Dekker
Copy link
Collaborator

pixi.lock was regenerated locally on a Windows 10 laptop, by

pixi.exe install -a

@thewtex Thanks for explaining this mechanism! By the way, it still produces a warning, on Windows:

WARN The activation script 'D:\src\ITKElastix\itk_wasm_env.bash' does not have the correct extension for the platform 'win-64'. The extension should be '.bat'.

Any suggestion? It seems a bit silly to just copy the bash file to .bat. And I ran it is GitBash so it should know bash (but it doesn't, apparently)

pixi.lock was regenerated locally on a Windows 10 laptop, by

    pixi.exe install -a

Co-authored-by: Matthew McCormick <[email protected]>
@thewtex
Copy link
Member

thewtex commented Mar 10, 2025

And I ran it is GitBash so it should know bash (but it doesn't, apparently)

Yes, emitting this may be a bug in pixi.

Conda / conda-forge / pixi currently use bash .sh for Unix and .bat for Windows by default, although there is WIP for a unified shell script.

@N-Dekker
Copy link
Collaborator Author

Thanks Matt! Shall we then postpone this PR until the pixi bat/bash issue is resolved (possibly by moving to a unified shell script)?

@thewtex
Copy link
Member

thewtex commented Mar 11, 2025

@N-Dekker yes, we could postpone

@N-Dekker
Copy link
Collaborator Author

OK, I'll leave it open for a few weeks to see if someone comes with a solution to the bash/bat shell script problem. Otherwise I'll close it, considering the PR "postponed". Unless someone else has closed it in the mean time 😸

Anyway, it was a good leaning experience for me to make my first pixi.lock fine 😃 Thanks Matt!

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.

2 participants