Skip to content
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.

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

Enhancement - Add export of installed packages to packages.config file #7

Closed
chrissie1 opened this issue Feb 11, 2013 · 7 comments
Closed
Labels
Feature Issues that introduce new functionality to the project, instead of updating existing functionality
Milestone

Comments

@chrissie1
Copy link
Contributor

I want to add an export of installed packages in JSON format so that you can save it and import and install those packages on another machine.

Suggested enhancement:
Allow the option to generate Boxstarter URL for selected packages as well.

@ghost ghost assigned chrissie1 Feb 11, 2013
@bsara
Copy link

bsara commented Oct 7, 2013

Why not just use a the same format as package.config XML file used by NuGet? It would make sense to me to export to what is already supported.

@gep13
Copy link
Member

gep13 commented Oct 8, 2013

Yes, I think that would make a lot of sense. I know there is an open issue on the Chocolatey site to fully support this natively in chocolatey, so if that comes together, we could be able to make use of that functionality.

@gep13 gep13 modified the milestones: 0.13, 0.12 Feb 18, 2014
@lofidevops
Copy link

If/when this does come together, the ability to select a subset of installed packages to export would be a great enhancement. Also/alternatively, could you generate a Boxstarter URL for a set of packages?

@gep13
Copy link
Member

gep13 commented Sep 18, 2014

Thanks for the interest!

Ooo, hadn't thought of generating a Boxstarter URL, but I think that this is a great idea! I reckon @mwrock would like it as well :-)

@mwrock
Copy link
Member

mwrock commented Sep 18, 2014

👍

@gep13 gep13 removed the 0 - Backlog label Feb 10, 2015
@gep13
Copy link
Member

gep13 commented Mar 24, 2015

What do you think of the following:

image

This simply generates a packages.config file, in the following format:

image

Which contains all of the currently installed packages.

If people are happy with this, we can look to extend this to include the ability to generate a chocolatey package with all the currently installed packages as dependencies, and create a boxstarter script that will have all entries as a single command.

Thoughts?

gep13 added a commit that referenced this issue Mar 24, 2015
- Using a simple PersistenceService, i.e. Open/Save Dialog
- Provide option to export the current list of installed packages to a packages.config file
gep13 added a commit that referenced this issue Mar 24, 2015
- Use XmlWriter, rather that StreamWriter
- While the file is being created, prevent the Export button from being
pushed again
@gep13
Copy link
Member

gep13 commented Mar 24, 2015

I am going to break this issue into two, one for export, and one for import.

@gep13 gep13 changed the title Enhancement - Add export and import of installed packages Enhancement - Add export of installed packages to packages.config file Mar 24, 2015
@gep13 gep13 closed this as completed Mar 25, 2015
RichiCoder1 pushed a commit to RichiCoder1/ChocolateyGUI that referenced this issue Jun 29, 2015
- Using a simple PersistenceService, i.e. Open/Save Dialog
- Provide option to export the current list of installed packages to a packages.config file
RichiCoder1 pushed a commit to RichiCoder1/ChocolateyGUI that referenced this issue Jun 29, 2015
- Use XmlWriter, rather that StreamWriter
- While the file is being created, prevent the Export button from being
pushed again
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature Issues that introduce new functionality to the project, instead of updating existing functionality
Projects
None yet
Development

No branches or pull requests

5 participants