Add option to include pinned-state in the choco export command

[Cyber1000]

Similar to #2503 where install-args are included in export-file, I would like to have pinned-state included in export.
I'm aware that pinned state isn't known at install time, but it would be helpful to get the same state on a new computer as before.

For now I'm helping myself without "choco export" (I've using this longer than "choco export" exists):

(choco pin -y |%{$_ -replace '(.+?)|(.+)','choco install $1 --version $2'} | select -Skip 1) >C:\Backup\choco.install.ps1
(choco pin -y |%{$_ -replace '(.+?)|.+','choco pin add -n=''$1'''} | select -Skip 1)>>C:\Backup\choco.install.ps1
"choco install -y",[string]::Join(" ", (clist -l -r |%{$_ -replace '(.+?)|.+','$1'} | select)) -join " " >>C:\Backup\choco.install.ps1

• first line writes install command for all pinned packages
• second line writes a "pin" for all pinned packages
• third line writes rest of packages
• On new computer I just have to execute C:\Backup\choco.install.ps1 (I don't have special install arguments, pins where more important to me)

Would be nice if choco implements an export fully (with pins).
Thanks!

[TheCakeIsNaOH]

To implement this, it will require that #798 is completed first, as that will add the ability to pin a package during install. And basing this on #2503 might be ideal, as there is likely some shared code between these two.

One item for discussion is whether the pin status should be included in --include-remembered-arguments, or if a separate argument (e.g. --include-pins) should be added.

[gep13]

@TheCakeIsNaOH said...
One item for discussion is whether the pin status should be included in --include-remembered-arguments, or if a separate argument (e.g. --include-pins) should be added.

This is an interesting question. Since if #798 is implemented, this would mean that a pinned package can be done by both an argument, and as a dedicated command. My gut says that this information would be included by default with the --include-remembered-arguments option, but perhaps a number option would be included to --exclude-pins.

Thoughts?

[Cyber1000]

Another option would be to always include it with the --include-remembered-arguments and have an option when installing, like so: choco install packages.config --ignore-pins

[TheCakeIsNaOH]

Thoughts?

I wouldn't have any issues with that on my end. I can see situations where pins might specifically want to be excluded, having a --exclude-pins would work for that. So either that, or my suggestion of a --include-pins would work, and don't really have strong feelings either way.

and have an option when installing, like so: choco install packages.config --ignore-pins

I don't thing this is ideal, at least not as the only option. It could work code wise, I actually have a PR in for that exact flag for the upgrade command.

My ideal endgame for the packages.config is that I can run choco install packages.config, and all the options I need are included inside the file. It is for the same reason I like docker-compose rather than using docker directly most the time. I can stick the information about how I am running the container into docker-compose.yml file, then run docker-compose up to start it up, and the file can get backed up, no need to remember or separately document what options I ran it with.

So having a way to configure if I want the pins exported is ideal, because then upon reinstall, there is not a need to remember to specify another command line argument, all the information about what options I want to use is already included in the file.