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

Make packages.config work again #10

Closed
ferventcoder opened this issue Jan 11, 2015 · 0 comments · Fixed by #42
Closed

Make packages.config work again #10

ferventcoder opened this issue Jan 11, 2015 · 0 comments · Fixed by #42

Comments

@ferventcoder
Copy link
Member

This resolves chocolatey-archive/chocolatey/issues/472

@ferventcoder ferventcoder added this to the 0.9.9 milestone Jan 11, 2015
@ferventcoder ferventcoder self-assigned this Jan 17, 2015
ferventcoder added a commit to ferventcoder/choco that referenced this issue Jan 25, 2015
ferventcoder added a commit to ferventcoder/choco that referenced this issue Jan 25, 2015
Split config file names off of the package names list for further
processing. Continue processing normal package names.
ferventcoder added a commit to ferventcoder/choco that referenced this issue Jan 25, 2015
ferventcoder added a commit to ferventcoder/choco that referenced this issue Jan 25, 2015
Configuration for serializing values for the config file.
ferventcoder added a commit to ferventcoder/choco that referenced this issue Jan 25, 2015
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 added a commit to ferventcoder/choco that referenced this issue Feb 1, 2015
ferventcoder added a commit to ferventcoder/choco that referenced this issue Feb 1, 2015
Split config file names off of the package names list for further
processing. Continue processing normal package names.
ferventcoder added a commit to ferventcoder/choco that referenced this issue Feb 1, 2015
ferventcoder added a commit to ferventcoder/choco that referenced this issue Feb 1, 2015
Configuration for serializing values for the config file.
ferventcoder added a commit to ferventcoder/choco that referenced this issue Feb 1, 2015
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 added a commit to ferventcoder/choco that referenced this issue Feb 4, 2015
ferventcoder added a commit to ferventcoder/choco that referenced this issue Feb 4, 2015
Split config file names off of the package names list for further
processing. Continue processing normal package names.
ferventcoder added a commit to ferventcoder/choco that referenced this issue Feb 4, 2015
ferventcoder added a commit to ferventcoder/choco that referenced this issue Feb 4, 2015
Configuration for serializing values for the config file.
ferventcoder added a commit to ferventcoder/choco that referenced this issue Feb 4, 2015
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 added a commit to ferventcoder/choco that referenced this issue Feb 4, 2015
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.
ferventcoder added a commit to ferventcoder/choco that referenced this issue Feb 4, 2015
ferventcoder added a commit to ferventcoder/choco that referenced this issue Feb 4, 2015
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 issue Feb 4, 2015
ferventcoder added a commit that referenced this issue Feb 21, 2015
Backup configuration files as a native way to keep around the
configuration file so that it can be compared to the new one that
overwrite the old (based on the merge strategy from nuget). This is
naive yes, more of GH-10 will later handle this better.
ferventcoder added a commit that referenced this issue Feb 21, 2015
* stable:
  (specs) Upgrade Scenarios
  PkgSvc - Fault tolerance failure location
  (specs) fix upgrade scenario specs
  Warn about locked files
  Invoke continue action w/error / catch upgrade error
  (maint) formatting/comment
  PkgSvc - Check to see if Install Location exists
  PkgInfoSvc - do nothing if IPackage is null
  Only run posh if packageResult is successful
  (GH-10) Backup configuration files
  IFileSystem Get Files by multiple extensions
  (specs) Reduce retries on filesystem for specs
  IFileSystem - convert to Enumerate Files/Directories
  Remove container binding log initialization
  (doc) fix xml comment
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants