Can I Include An MSI File Inside A Chocolatey Package?


Answer :

Yes, this is definitely possible. This is actually exactly what the ChocolateyGUI package does. You can see its .nuspec file here:

https://github.com/chocolatey/ChocolateyGUI/blob/develop/nuspec/chocolatey/ChocolateyGUI.nuspec

<?xml version="1.0"?> <package>   <metadata>     <id>chocolateygui</id>     <version>$version$</version>     <title>Chocolatey GUI</title>     <authors>Chocolatey</authors>     <owners>Chocolatey</owners>     <projectUrl>https://github.com/chocolatey/ChocolateyGUI</projectUrl>     <projectSourceUrl>https://github.com/chocolatey/ChocolateyGUI</projectSourceUrl>     <packageSourceUrl>https://github.com/chocolatey/ChocolateyGUI/tree/develop/nuspec/chocolatey</packageSourceUrl>     <iconUrl>https://raw.githubusercontent.com/chocolatey/choco/master/docs/logo/chocolateyicon.gif</iconUrl>     <licenseUrl>https://raw.githubusercontent.com/chocolatey/ChocolateyGUI/develop/LICENSE</licenseUrl>     <bugTrackerUrl>https://github.com/chocolatey/ChocolateyGUI/issues</bugTrackerUrl>     <requireLicenseAcceptance>false</requireLicenseAcceptance>     <description> Chocolatey GUI is a nice GUI on top of the Chocolatey command line tool.  ## Features  * View all **installed** and **available** packages * **Update** installed but outdated packages * **Install** and **uninstall** packages * See detailed **package information**  ## Notes This package will only work correctly on Windows 7 SP1 through Windows 10 (1708) or     Windows Server 2008 R2 SP1 through Windows Server 2016, and requires .NET Framework     4.5.2 at minimum.   </description>     <summary>A GUI for Chocolatey</summary>   <releaseNotes> All release notes for Chocolatey GUI can be found on the GitHub site -     https://github.com/chocolatey/ChocolateyGUI/releases   </releaseNotes>     <tags>chocolateygui chocolatey admin foss</tags>     <dependencies>       <dependency id="Chocolatey" version="[0.10.3, 0.11)" />     </dependencies>   </metadata>   <files>     <file src="chocolateyInstall.ps1" target="tools"/>     <file src="chocolateyUninstall.ps1" target="tools"/>     <file src="..\..\BuildArtifacts\ChocolateyGUI.msi" target="tools"/>     <file src="..\..\LICENSE" target="tools\LICENSE"/>     <file src="VERIFICATION.txt" target="tools"/>   </files> </package>

Then, as you pointed out, you would then use Install-ChocolateyInstallPackage to perform the installation, which would then use the local MSI within the package, rather than first downloading it. You can see the installation script for ChocolateyGUI here:

https://github.com/chocolatey/ChocolateyGUI/blob/develop/nuspec/chocolatey/chocolateyInstall.ps1

$ErrorActionPreference = 'Stop'; $toolsDir     = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)" $fileLocation = Join-Path $toolsDir 'ChocolateyGUI.msi'  $packageArgs = @{   packageName   = $env:ChocolateyPackageName   softwareName  = 'Chocolatey GUI'   file          = $fileLocation   fileType      = 'msi'   silentArgs    = "/qn /norestart /l*v `"$env:TEMP\$env:ChocolateyPackageName.$env:ChocolateyPackageVersion.log`""   validExitCodes= @(0,1641,3010) }  Install-ChocolateyInstallPackage @packageArgs  Remove-Item -Force $packageArgs.file

You can do the exact same thing with an ISO image file, and there is a walkthrough on the established best practice for using that ISO file here:

How To Mount An Iso In Chocolatey Package

NOTE: If you are planning on pushing the package to Chocolatey.org, please bear in mind the size of the MSI/ISO file. If this is especially large, it is probably best not to include it within the nupkg, but rather use a download link.


Like Gary said, you can include arbitrary files in the package.

I'd emphasize that it's not a great idea. You have to download the package file itself (that's what happens when you choco install foo). Moving the MSI/ISO inside the package means you'll be downloading it with the package file and, depending on the size, slowing down feedback at the console.

Using the proper helpers and external URLs gives you a lot of great behaviors, least of which, is the download progress bar!

If file storage is a problem, there are many free options including: GitHub, Google Drive, DropBox, etc. If you're creating "internal" packages for your company, a network share can work with file:// URLs.


Comments

Post a Comment

Popular posts from this blog

Converting A String To Int In Groovy

Answer : Use the toInteger() method to convert a String to an Integer , e.g. int value = "99".toInteger() An alternative, which avoids using a deprecated method (see below) is int value = "66" as Integer If you need to check whether the String can be converted before performing the conversion, use String number = "66" if (number.isInteger()) { int value = number as Integer } Deprecation Update In recent versions of Groovy one of the toInteger() methods has been deprecated. The following is taken from org.codehaus.groovy.runtime.StringGroovyMethods in Groovy 2.4.4 /** * Parse a CharSequence into an Integer * * @param self a CharSequence * @return an Integer * @since 1.8.2 */ public static Integer toInteger(CharSequence self) { return Integer.valueOf(self.toString().trim()); } /** * @deprecated Use the CharSequence version * @see #toInteger(CharSequence) */ @Deprecated public static Integer toInteger(String self) { return toInteg
Read more

"Cannot Create Cache Directory /home//.composer/cache/repo/https---packagist.org/, Or Directory Is Not Writable. Proceeding Without Cache"

Answer : if anyone pass through here, this is shorter solution: sudo chown -R $USER $HOME/.composer it seems to me the group information is missing in your command sudo chown -R <user> /home/<user>/.composer/cache/repo/https---packagist.org Shoud be sudo chown -R <user>:<group> /home/<user>/.composer/cache/repo/https---packagist.org But to avoid other permission issues, I would rather advise: sudo chown -R <user>:<group> /home/<user>/.composer/cache (you'll need access to other folders in there) and sudo chown <user>:<group> /home/<user>/.composer To make sure your user has permissions enough on the global composer folder. Mind the missing recursion so the user don't own keys created by root. If you need to find out the group: groups <user>
Read more

Android How Can I Convert A String To A Editable

Answer : As you probably found out, Editable is an interface so you cannot call new Editable() . However an Editable is nothing more than a String with Spannables, so use SpannableStringBuilder: Editable editable = new SpannableStringBuilder("Pass a string here"); If you only want to change the Spannables, never the text itself, you can use a basic SpannableString. Use Editable.Factory.getInstance().newEditable(str) From the android documentation: Returns a new SpannedStringBuilder from the specified CharSequence. You can override this to provide a different kind of Spanned.
Read more