Multiple destinations about npackd-cpp

[gergelyk]

Thanks 👍

[tim-lebedkov]

One of the reasons to modify the default installation path is missing free disk space on C:. Defining the target directory in the repository .xml file would be wrong in this case.

What are the criteria for deciding where a particular package should be installed?

[nodiscc]

What are the criteria for deciding where a particular package should be installed?

A global setting allowing to specify a destination directory (or at least, drive letter) would be nice to have (either through GUI or a config file). _{Btw @tim-lebedkov thanks for reviewing Mixxx and adding the 32-bit version!}

[gergelyk]

In my case its the type of the package would decide where to install it. For example regular applicatins go to "C:\Program Files". But I also use npackd to distribute my deliverables to the buddies. This kind of packages would be stored in e.g. "C:\Deliverables". It's not the most critical issue though...

[tim-lebedkov]

Github does not have issue votes. Let me know If you have any "critical" issues.

[tim-lebedkov]

Another way would be to create a file system link from "C:\Deliverables\MyPackage" to "C:\Program Files\MyPackage"

[gergelyk]

True. Thank you for suggestions!