Specifying a nested path sounds good to me.

I am thinking of the following behavior:

• without a path separator in the string -> search for executable in the typical directories with all possible file extensions

pixi global install python=3.9 --expose=python3.9=python

• with path separator -> we expect the relative path to the env root. The extension would have to be mentioned in that case

pixi global install dotnet  --expose "dotnet=lib\dotnet\dotnet.exe"

Thank you for your answer, unfortunately I tried before but it fails too.

pixi global install dotnet  --expose "dotnet=dotnet\dotnet.exe"

returns :

× Couldn't install packages. Reverting also failed.
  ├─▶ Failed to add executables for environment: dotnet
  ╰─▶ Couldn't find executable dotnet in C:\Users\bahugo\.pixi\envs\dotnet, found these executables: []

dotnet executable is not in lib directory, it's located here :

Yes @bahugo, I was outlining a possible implementation. Sorry if that wasn't clear.

@ruben-arts suggested to never specify the file extension, even for nested paths.

@Hofer-Julian, my bad, I read to fast...
It sounds great to me.