Skip to content

Conversation

Isopolito
Copy link
Contributor

@Isopolito Isopolito commented Mar 20, 2017

Hi, I made the changes for issue #962 and submitted them on this PR. I'm still working out how to get the unit test(s) created for it, but in the meantime i wanted to submit this since I have a few questions:

  • Is deep copying a config and only changing PackageNames to what should be upgraded sufficient (line 1337), or do other things need to be modified in the new config before sending it off to upgrade_run?

  • Is just removing a package name from config.PackageNames (line 1332) enough to make it disappear from the install process?

Thanks!

ahall added 2 commits March 20, 2017 17:37
When install command is called on a pacakge, upgrade that package if
already installed and a higher version is specifiied on the commmand
line
@ferventcoder
Copy link
Member

ferventcoder commented Mar 20, 2017

@Isopolito it may be best to wait for #1132 to be implemented so you won't need to handle upgrades against packages.config files.

@ferventcoder
Copy link
Member

Also, please read CONTRIBUTING - it does state we never want to see merge commits in pull requests.

Copy link
Member

@ferventcoder ferventcoder left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These changes regarding a packages.config file should wait for implementation of the upgrades with packages.config.

Please back out the merge commit and read over CONTRIBUTING for the correct way to do pull in updated changes.

@Isopolito
Copy link
Contributor Author

Sorry about that, I'm new to this process. I read over contributing but still messed that up. I'll look over #1132 and wait for that to be implemented. Is there a preferred way to back out the merge commit?

@ferventcoder
Copy link
Member

Is there a preferred way to back out the merge commit?

@Isopolito Yes, choco install gitextensions, ensure that gets configured appropriately and use it to help you back up to the older commit, then do a force push back to the branch on that (but be careful, force pushes should only be used in feature branches). We have an example of this in contributing.

@CLAassistant
Copy link

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.


ahall seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
You have signed the CLA already but the status is still pending? Let us recheck it.

@gep13 gep13 changed the title (GH-962) Upgrade outdated on install (#962) Upgrade outdated on install Oct 15, 2021
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.

Before modify script not called when install command is used to upgrade
3 participants