Skip to content

Instantly share code, notes, and snippets.

Embed
What would you like to do?
Export installed Chocolatey packages as packages.config - thanks to Matty666
#Put this in Export-Chocolatey.ps1 file and run it:
#Export-Chocolatey.ps1 > packages.config
#You can install the packages using
#choco install packages.config -y
Write-Output "<?xml version=`"1.0`" encoding=`"utf-8`"?>"
Write-Output "<packages>"
choco list -lo -r -y | % { " <package id=`"$($_.SubString(0, $_.IndexOf("|")))`" version=`"$($_.SubString($_.IndexOf("|") + 1))`" />" }
Write-Output "</packages>"
@wolfmagic7

This comment has been minimized.

Copy link

commented Feb 2, 2017

this would be the command line to run on my old laptop that i then import into new laptop (i presume). can you tell me where i would find the resulting script and what it would be called? would it be easy enough to edit out packages i dont want on the new machine or would it be easier to do that in the gui version? thanks.

@rowellx68

This comment has been minimized.

Copy link

commented Feb 8, 2017

Here's a version that specifically installs the version

choco list -lo -r -y | % { "choco install " + $_.Replace("|", " -version ") + " -y" }

@wolfmagic7 You can just pipe it to a file, something like this:

choco list -lo -r -y | % { "choco install " + $_.Replace("|", " -version ") + " -y" } > Install.ps1

And you should be in the directory where you ran the script.

@claudiuconstantin

This comment has been minimized.

Copy link

commented Mar 30, 2017

'%' is not recognized as an internal or external command, operable program or batch file
Any idea?

@donbing

This comment has been minimized.

Copy link

commented Apr 4, 2017

use power shell

@Matty666

This comment has been minimized.

Copy link

commented Jul 5, 2017

I've changed this to write the output as a package.config file rather than individual choco install commands.

Write-Output "<?xml version=`"1.0`" encoding=`"utf-8`"?>"
Write-Output "<packages>"
choco list -lo -r -y | % { "   <package id=`"$($_.SubString(0, $_.IndexOf("|")))`" version=`"$($_.SubString($_.IndexOf("|") + 1))`" />" }
Write-Output "</packages>"

Put this in export.ps1 file and run it:

export.ps1 > packages.config

You can install the packages using

choco install packages.config -y

I prefer this because chocolatey will tell you which packages were successful etc. When running the original install.ps1 and some packages fail you don't really see them as it seems to just continue

@farmerbean

This comment has been minimized.

Copy link

commented Jul 17, 2017

Nice @Matty666 - I dropped your script into a file, then put a wrapper round it so I can pump the whole thing to my onedrive folder and run a scheduled daily task to back it all up!

.\choco_backup.ps1 | out-file backup.config
$filenameFormat = (Get-Date -Format "yyyy-MM-dd") + "_"+ "backup.config"
Rename-Item -Path "backup.config" -NewName $filenameFormat
Return

Then run a Windows scheduled task (daily, in my case):

program/script: "c:\windows\system32\WindowsPowershell\v1.0\powershell.exe"
Add arguements: "-ExecutionPolicy Bypass C:\Users\badhatharry\OneDrive\System\Choco\choco_wrapper.ps1"
Start in: "C:\Users\badhatharry\OneDrive\System\Choco\"
@bcurran3

This comment has been minimized.

Copy link

commented Aug 9, 2017

Hey guys!

@itopiacloud pointed me in this direction awhile ago when I was contemplating creating a script to backup my Chocolatey packages list.

I read this thread but the methods here just didn't go as far as I wanted, so I made a backup script as well. Not one for re-inventing the wheel, I couldn't have done it without @alimbada and @rowellx68's parsing. (I suck at parsing.) So thank you guys!

So here's me efforts, getting by a with a little help from my friends:
https://chocolatey.org/packages/choco-package-list-backup

@alimbada

This comment has been minimized.

Copy link
Owner Author

commented Nov 29, 2017

I've updated the script with @Matty666's suggestions.

Apologies for the tardy response here; GitHub doesn't send notifications for comments on gists.

@mustafakibar

This comment has been minimized.

Copy link

commented Jan 29, 2019

Here's a version that specifically installs the version

choco list -lo -r -y | % { "choco install " + $_.Replace("|", " -version ") + " -y" }

@wolfmagic7 You can just pipe it to a file, something like this:

choco list -lo -r -y | % { "choco install " + $_.Replace("|", " -version ") + " -y" } > Install.ps1

And you should be in the directory where you ran the script.

Without version information:

choco list -lo -r -y | % { "choco install " + $_.split('|')[0] + " -y" } > Install.ps1

@valentijnscholten

This comment has been minimized.

Copy link

commented Apr 29, 2019

Thanks for the script. I kept running into a deserialization error on the xml header when installing on the new machine.

<?xml encoding="utf-8"?>

After trying all kinds of stuff, different encoding, including version, excluding encoding etc. etc. Still couldn't user the packages.config to install the packages. Turns out you can just remove the whole xml header and everything install fines :)

So just

<packages>
...
</packages>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.