Skip to content
This repository has been archived by the owner on Feb 19, 2019. It is now read-only.

[Enhancement] Restore packages from a 'packages.config' file #31

Closed
AnthonyMastrean opened this issue Nov 30, 2011 · 8 comments
Closed

Comments

@AnthonyMastrean
Copy link
Contributor

The NuGet way, nuget install packages.config, only downloads the packages. The idea being, you've already installed the packages into the projects, you're just rebuilding a new machine/workspace. Obviously, chocolatey would have different semantics: rebuild a machine from this "manifest" (reinstall or update packages).

chocolatey install packages.config

or

cinst packages.config
@ferventcoder
Copy link
Contributor

I like it.

@ferventcoder
Copy link
Contributor

I would totally dig a pull request here ;)

@ferventcoder
Copy link
Contributor

This has been completed in #43

@ferventcoder
Copy link
Contributor

For notes of others, this packages.config differs a little from a vanilla nuget's packages.config in that it adds a source element. For example:

<packages>
    <package id="somepackage"   />
    <package id="somepackagewithversion" version="1.0"  />
    <package id="somepackagewithsource" version="1.0" source="http://myget.org/f/customfeed" />
    <package id="IISExpress" source="webpi" />
</packages>

@bennage
Copy link

bennage commented Feb 10, 2012

Can chocolatey generate a package file based on what's currently installed? Or is that still manual?

@ferventcoder
Copy link
Contributor

That is an interesting idea. You want to log a new issue for it (or would you like me to)? I'm curious in how we could get the items that are from different sources... and also how to account for items that never end up in lib (ruby gems and WebPI items)

@AnthonyMastrean
Copy link
Contributor Author

I submitted issue #67 to track the idea.

@bennage
Copy link

bennage commented Feb 16, 2012

Thanks! I love this project btw.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants