New package: direnv.direnv 2.32.2

[mloskot]

• Have you signed the Contributor License Agreement?
• Have you checked that there aren't other open pull requests for the same manifest update/change?
• This PR only modifies one (1) manifest
• Have you validated your manifest locally with winget validate --manifest <path>?
• Have you tested your manifest locally with winget install --manifest <path>?
• Does your manifest conform to the 1.4 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

---

---

Microsoft Reviewers: Open in CodeFlow

[wingetbot]

   

[wingetbot]

/AzurePipelines run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[microsoft-github-policy-service]

mloskot,

The check-in policies require a moderator to approve PRs from the community.

Our moderators are community volunteers, please be patient and allow them sufficient time to review your submission.

Template: msftbot/requiresApproval/moderator

[microsoft-github-policy-service]

Hello mloskot,
Validation has completed.

Template: msftbot/validationCompleted

[wingetbot]

Publish pipeline succeeded for this Pull Request. Once you refresh your index, this change should be present.

[Eason0210]

This don't works when I use powersell to install direnv, because It can not create symlink.

It works well with CMD.

[mloskot]

@Eason0210 The yellow message "Command line alias added" indicates executable was (hard or sym)link-ed in that Links folder. The winget tries to avoid polluting your PATH with numerous entries, trying to put exeutable aliases in Links as common location. The \Links features is a reason to run winget as Administrator - see this for details #99059 (comment)

[Eason0210]

@mloskot,

Thanks for your information.
I tried to install direnv in powershell with Administrator, It works as expected.