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.

Sign up for GitHub

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

Jump to bottom

Achieve near 100% compatibility with older POSH chocolatey client #54

Closed
4 tasks done
ferventcoder opened this issue Feb 2, 2015 · 3 comments
Closed
4 tasks done

Achieve near 100% compatibility with older POSH chocolatey client #54

ferventcoder opened this issue Feb 2, 2015 · 3 comments
Assignees
@ferventcoder
Labels
5 - Released CoreTeam FeatureParity Improvement
Milestone
0.9.9

Comments

@ferventcoder
Copy link
Member

  • Bring back sources
  • Allow default push source but deprecate the option.
  • choco version deprecation
  • choco update deprecation

The rest will be handled in linked tickets. #42, #52
@ferventcoder ferventcoder self-assigned this Feb 2, 2015
@ferventcoder ferventcoder added this to the 0.9.9 milestone Feb 2, 2015
ferventcoder added a commit that referenced this issue Feb 3, 2015
@ferventcoder
(GH-54) Deprecate "sources" command
bf0e21e
@ferventcoder
Copy link
Member Author

@DarwinCSIWindowscom These options should make choco almost 100% compatible with the older version (in what to pass to the commands anyway). I went through each of the commands and put a note up top on how compatible they are with previous versions.

@ferventcoder
Copy link
Member Author

https://github.com/chocolatey/choco/wiki/CommandsPush

@ferventcoder
Copy link
Member Author

As far as general compatibility, we are nearly 100% compatible with the previous version of choco. So many tools that use choco may be able to upgrade to the new version with one setting and operate just fine.

@ferventcoder ferventcoder changed the title Bring back some removed settings and deprecate them Make new choco nearly 100% compatible with older POSH chocolatey client Feb 3, 2015
@ferventcoder ferventcoder changed the title Make new choco nearly 100% compatible with older POSH chocolatey client Achieve near 100% compatibility with older POSH chocolatey client Feb 3, 2015
ferventcoder added a commit that referenced this issue Feb 3, 2015
@ferventcoder
(GH-54) Sources command updates/specs
e5c02ce
ferventcoder added a commit that referenced this issue Feb 3, 2015
@ferventcoder
(GH-54) Push command default source
ced4bce 
Deprecate default source with a message.
ferventcoder added a commit that referenced this issue Feb 3, 2015
@ferventcoder
(GH-54) shim for cver points to version
848f91b 
To allow for the deprecation notice to go through successfully,
redirect cver back to version.
ferventcoder added a commit that referenced this issue Feb 3, 2015
@ferventcoder
(GH-54) version command deprecation
6b20a17 
Bring back version command and deprecate it for v1.
ferventcoder added a commit that referenced this issue Feb 3, 2015
@ferventcoder
(GH-54) update default push feed deprecation note
6b5f041
ferventcoder added a commit that referenced this issue Feb 3, 2015
@ferventcoder
(GH-54) update command deprecation
7dc02e0 
Bring back update command and properly deprecate it for v1 to later be
replaced with what will perform the package index updates.
This was referenced Feb 3, 2015
Merged
Closed
ferventcoder added a commit to ferventcoder/choco that referenced this issue Feb 3, 2015
@ferventcoder
(chocolateyGH-54) add setapikey
baf13ff 
This is more of a nuget parity thing, as it is uses setapikey for
setting keys.
ferventcoder added a commit that referenced this issue Feb 4, 2015
@ferventcoder
(GH-54) Fix -version error
51d59c8 
When option parsing attempts to parse -version, it sees it as a bundled
option because it finds -v as short option for verbose, so it errors on
-e, which isn't a short option. Instead it should not error and allow
the option to be picked up by possibly another set of option parsing.
ferventcoder added a commit that referenced this issue Feb 4, 2015
@ferventcoder
(GH-54) Show help menu when unparsed options
17e259a 
If there are any unparsed switches/options after parsing is considered
complete, then show the help menu. This is introduced to address a
minor regression introduced by
51d59c8
, where the help menu would no longer be shown if an option was not
parsed. It was previously handling this by throwing an error that would
cause the help menu to show up. However b/c of the way the bundled
option parsing is done, coupled with multiple passes through the
parser, some options may be misinterpreted as bundled options and throw
errors, which was corrected in the linked commit.

Add additional behavior to detect unparsed args and show the help menu
instead of attempting to roll with it.
ferventcoder added a commit that referenced this issue Feb 6, 2015
@ferventcoder
(GH-54) Undeprecate default push source
f9c6b42 
Ha! Just kidding, don't deprecate default push source. Leave it set
to chocolatey.org for now.
ferventcoder added a commit that referenced this issue Feb 6, 2015
@ferventcoder
(GH-54)(spec) Fix specs for default push source
4b1e6f0
@aronovgj aronovgj mentioned this issue Feb 6, 2015
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ferventcoder ferventcoder

Labels
5 - Released CoreTeam FeatureParity Improvement
Projects
None yet
Milestone
0.9.9
Development

No branches or pull requests
2 participants
@ferventcoder @gep13