Skip to content
This repository has been archived by the owner on Jul 14, 2021. It is now read-only.

Windows elevated / non-elevated installation should be user selectable #136

Closed
adamedx opened this issue Aug 13, 2014 · 2 comments
Closed
Labels
Aspect: Packaging Distribution of the projects 'compiled' artifacts. Platform: Windows

Comments

@adamedx
Copy link

adamedx commented Aug 13, 2014

Users should be able to choose whether or not to install the chef-dk msi with elevated (root) privileges. Additionally, whatever install directory is chosen should be validated as to whether or not it has a space since Ruby and its toolsets behavior erratically when executables are located in a path that contains spaces.

From an MSI perspective, this forum post describes how this can be authored via Wix: http://stackoverflow.com/questions/14339372/wix-non-admin-installer-tutorial.

@irvingpop
Copy link

This should be worked on after #68 is fully resolved (ChefDK can be installed into a path with spaces or on a non-system drive)

@danielsdeleo
Copy link
Contributor

Not doing this.

@jkeiser jkeiser added the wontfix label Feb 9, 2016
@chef-boneyard chef-boneyard locked and limited conversation to collaborators Feb 14, 2018
@tas50 tas50 added Platform: Windows Aspect: Packaging Distribution of the projects 'compiled' artifacts. and removed Area: Windows labels Jan 2, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Aspect: Packaging Distribution of the projects 'compiled' artifacts. Platform: Windows
Development

No branches or pull requests

6 participants