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

(GH-10) Packages.config #42

Conversation

ferventcoder
Copy link
Member

If a config file is specified, use that to determine settings for each
package to install. Clone the config and make adjustments based on what
is in the packages.config file for that particular package.

Closes #10

@ferventcoder
Copy link
Member Author

This makes one change to the packages.config file - it now needs this setup:

The packages.config can be set up with the following elements:

<?xml version="1.0" encoding="utf-8"?>
<packages>
    <package id="apackage" />
    <package id="anotherPackage" version="1.1" />
    <package id="chocolateytestpackage" version="0.1" source="somelocation" />
    <package id="chocolateytestpackage" version="0.1" source="somelocation" 
      installArguments="" packageParameters="" forceX86="false" 
      allowMultipleVersions="false" ignoreDependencies="false" 
     />
</packages>

Note the surrounding <chocolatey> tag.

This allows copying a complex object over so that changes can be made
without affecting the original object.
Split config file names off of the package names list for further
processing. Continue processing normal package names.
Configuration for serializing values for the config file.
If a config file is specified, use that to determine settings for each
package to install. Clone the config and make adjustments based on what
is in the packages.config file for that particular package.
@ferventcoder ferventcoder force-pushed the ticket/master/GH-10-packages.config branch from 5bdc256 to 108236e Compare February 4, 2015 09:00
The work of packages.config converted to package names and options is
done in ChocolateyPackageService, so there is no need to check in
NugetService. Remove the logic branch.
Use the original packages.config format to cause the least amount of
churn from users that have already created and invested in
packages.config files.
ferventcoder added a commit that referenced this pull request Feb 4, 2015
@ferventcoder ferventcoder merged commit 4c3059f into chocolatey:master Feb 4, 2015
@ferventcoder ferventcoder deleted the ticket/master/GH-10-packages.config branch February 4, 2015 09:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Make packages.config work again
1 participant