-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Need flag to disable setting system PATH variable #211
Comments
I'm not sure exactly how to do this, but the WIX installer (version 3) is used to build the MSI files. The relevant files are in https://github.com/StrawberryPerl/Perl-Dist-Strawberry/tree/master/share/msi You could alternately use the portable versions as these do not add to the global path. Berrybrew is also a good option. It uses portable versions and includes an option to turn off the current perl. https://github.com/dnmfarrell/berrybrew And as a general note, removing the Strawberry Perl path components typically needs to be an all or nothing approach. Many of the libraries installed with Strawberry Perl will not run unless they can access the DLLs in the |
Agreed that it is all or nothing. The envisioned case here is one where the caller would have the PATH set up to the requirements when calling Strawberry Perl. This line seems to be where the PATH is appended. Is there a "silent"/"unattended" install flag? |
Maybe this? https://learn.microsoft.com/en-us/windows/win32/msi/standard-installer-command-line-options#quiet |
Yes you are right, the standard |
The answer is probably the same as in #224 (comment) https://github.com/StrawberryPerl/Perl-Dist-Strawberry/tree/master/share/msi I have not worked through these files or the MSI process in any detail, so any findings you can note would be very helpful. |
The installer currently adds the Strawberry Perl bin folders to the system PATH environment variable. This is normally ok, but I need the ability to customize this. What is the installer flag to disable setting the PATH?
The text was updated successfully, but these errors were encountered: