8000 (googlechrome) Include master_preferences file · Issue #1603 · chocolatey-community/chocolatey-packages · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

(googlechrome) Include master_preferences file #1603

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.

Sign up for GitHub

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

Jump to bottom
Closed
TaffarelJr opened this issue Jan 12, 2021 · 5 comments
Closed

(googlechrome) Include master_preferences file #1603

TaffarelJr opened this issue Jan 12, 2021 · 5 comments
Labels
Enhancement Pending closure Up for grabs

Comments

@TaffarelJr
Copy link
TaffarelJr commented Jan 12, 2021 •
edited
Loading

When installing the Google Chrome Enterprise MSI, a file called master_preferences can be placed alongside chrome.exe in the install destination folder (%ProgramFiles%\Google\Chrome\Application\) to configure Chrome and control how it first launches.

It would be great if there was a flag on the Chocolatey package to specify a path to a master_preferences file to be included in the installation. Ideally we'd include both local drive & URI support.

Notes:

Expected Behavior

Examples:

choco install googlechrome --package-parameters="/PreferenceFile='C:\InstallFiles\master_preferences'"
choco install googlechrome --package-parameters="/PreferenceFile='C:\InstallFiles\initial_preferences.json'"
choco install googlechrome --package-parameters="/PreferenceFile='http://mydomain.com/InstallFiles/master_preferences'"

Each of these variants would install the Chrome enterprise MSI like normal, but then copy the specified file to the Chome install directory (%ProgramFiles%\Google\Chrome\Application\) as its final step.

The name of the file would not be changed from the specified name, but would overwrite any previously-existing file. (Chrome includes a very simple master_preferences file by default.)

Chocolatey would throw an exception if the specified file was not found, could not be downloaded, or otherwise could not be copied to the install directory.

Current Behavior

  1. Use Chocolatey to install Chome
  2. Copy/download master_preferences file from wherever I have it stored
  3. Handle any exceptions manually

Context

Mostly cosmetic; I'd love to be able to shrink all my Chocolatey installs to 1-liners, instead of requiring multiple lines & error handling to fully install and configure one app.
@TheCakeIsNaOH
Copy link
Member

Mostly cosmetic; I'd love to be able to shrink all my Chocolatey installs to 1-liners, instead of requiring multiple lines & error handling to fully install and configure one app.

chocolatey/choco#1185 is probably what you want.

@AdmiringWorm
Copy link
Member
AdmiringWorm commented Jan 12, 2021 •
edited
Loading

I agree with @TheCakeIsNaOH that it would be better served through a hook (which is what the linked issue is about).
But due to the lack of it, it is definitely something that could be implemented in the package itself.
Not sure if allowing downloading a file would be appropriate though (at least not without forcing the use of a checksum as well), but a local file is something that could be added.

@majkinetor
Copy link
Contributor

Whats wrong with cp ?

@stale
Copy link
stale bot commented Jun 22, 2021

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?

@stale
Copy link
stale bot commented Jul 30, 2021

Dear contributor,
because this issue seems to be inactive for quite some time now, I've automatically closed it. If you still feel this is a valid issue, please feel free to re-open the issue. Thank you for your contribution.

@stale stale bot closed this as completed Jul 30, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Enhancement Pending closure Up for grabs
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@majkinetor @AdmiringWorm @TaffarelJr @TheCakeIsNaOH
0