New package: Inkdrop.Inkdrop.Portable version 5.8.1

[CoolPlayLin]

Checklist for Pull Requests

• Have you signed the Contributor License Agreement?
• Is there a linked Issue?

Manifests

• 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.6 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).

[wingetbot]

/AzurePipelines run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[Trenly]

[Policy] Zip Binary

[CoolPlayLin]

Why zip-binary Depends on library files that aren't available via symlink ?

[Trenly]

Why zip-binary Depends on library files that aren't available via symlink ?

[CoolPlayLin]

But it can actually run normally

[Trenly]

But it can actually run normally

Not in all cases. If the user has Developer mode enabled, or runs the install as admin, then attempting to run inkdrop using the command line alias that gets added causes the paths to the DLLs to be unavailable.

PS C:\Users\WDAGUtilityAccount\Desktop\winget-pkgs> Get-ARPTable

DisplayName    : Microsoft Edge
DisplayVersion : 126.0.2566.1
Publisher      : Microsoft Corporation
ProductCode    : Microsoft Edge
Scope          : Machine

DisplayName    : Microsoft Edge Update
DisplayVersion : 1.3.187.37
Publisher      :
ProductCode    : Microsoft Edge Update
Scope          : Machine

DisplayName    : Inkdrop
DisplayVersion : 5.8.1
Publisher      : Inkdrop
ProductCode    : Inkdrop.Inkdrop.Portable__DefaultSource
Scope          : User

PS C:\Users\WDAGUtilityAccount\Desktop\winget-pkgs> inkdrop
# Did not launch
PS C:\Users\WDAGUtilityAccount\Desktop\winget-pkgs> where.exe inkdrop
C:\Users\WDAGUtilityAccount\AppData\Local\Microsoft\WinGet\Links\inkdrop.exe
PS C:\Users\WDAGUtilityAccount\Desktop\winget-pkgs> inkdrop
# Did not launch
PS C:\Users\WDAGUtilityAccount\Desktop\winget-pkgs> Invoke-Expression inkdrop
# Did not launch
PS C:\Users\WDAGUtilityAccount\Desktop\winget-pkgs> $env:Path -match [Regex]::Escape('C:\Users\WDAGUtilityAccount\AppData\Local\Microsoft\WinGet\Links')
True

[og-mrk]

But it can actually run normally

Not in all cases. If the user has Developer mode enabled, or runs the install as admin, then attempting to run inkdrop using the command line alias that gets added causes the paths to the DLLs to be unavailable.

Kind of curious on this particular situation, if the Command Alias won't work (that is, if the user installs the software as admin to make the Symbolic Link in the first place).. then couldn't we remove the PortableCommandAlias field entirely to partially resolve the zip-binary issue?

My apologies if the above suggestion/question might seem like a stupid idea, as I'm kind of new with this particular topic. Thanks in advance @Trenly 😄

[Trenly]

But it can actually run normally

Not in all cases. If the user has Developer mode enabled, or runs the install as admin, then attempting to run inkdrop using the command line alias that gets added causes the paths to the DLLs to be unavailable.

Kind of curious on this particular situation, if the CommandAlias won't work (that is, if the user installs the software as admin to make the Symbolic Link in the first place).. then can't we just remove the PortableCommandAlias field and partially resolve the zip-binary issue?

My apologies if the above suggestion/question might seem like a stupid idea, as I'm kind of new with this particular topic. Thanks in advance @Trenly 😄

No, removing the command alias doesn’t change the underlying behavior. WinGet will always attempt to add the program to PATH - if PortableCommandAlias isn’t set, then WinGet will just use the file name as the alias. And, since WinGet doesn’t add start menu entries or desktop icons for portable apps, the only ways to start the application are to use the command line, or navigate to the executable directly. So an admin install always results in a symlink, and a user install results in a symlink if developer mode is enabled, and if there are dll dependencies then the application won’t launch properly from the command line if a symlink is used.