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

Support pinned options per package #1372

Closed
bcurran3 opened this issue Jul 30, 2017 · 4 comments
Closed

Support pinned options per package #1372

bcurran3 opened this issue Jul 30, 2017 · 4 comments

Comments

@bcurran3
Copy link

bcurran3 commented Jul 30, 2017

PROBLEM:
There are a number of programs that vendors make available via a static download link so that end users can always get the latest version when they go to the website and download the program, i.e. http://softwaresite.com/program.exe. Chocolatey package maintainers then use this link when no version specific download link is available for the program. Examples of some of my packages include: drivermax, resilio-home, resilio-business, utorrent, and a few others. Many times a package maintainer can update their package for a new release of the software only to not know the very next day the vendor has updated the program and thus invalidated the Chocolatey package while sitting in moderation and the package fails installation for Chocolatey end users due to the checksums being wrong for the latest version of the program. This comes up prominently when Chocolatey users don't "cup all" frequently. Some Chocolatey users may only "cup all" once a week or even once a month to find that many packages have been updated and available only to find that many won't install because the program has been updated to a newer version than the package.

(Chocolatey Pro) I run "cup all" frequently. Every time I "cup all" and there is a new version of a package such as sysinternals that fails the virus check, I have to manually run "cup all --skip-virus-check" or "cup sysinternals --skip-virus-check" to get the updated program/s installed.

Basically I need to run cup 3 times to get all my packages/programs updated at times. Sysinternals just failed me twice due to needing --skip-virus-check and --ignore-checksums to install.

SOLUTION:
Have choco store and use "pinned options" for specified packages.

In the case of drivermax, the resilio packages, and utorrent, users could pin the option "--skip-virus-check" and it would update every time even if they have 1.1 installed, 1.2 is the latest package, and 1.3 is the current version. (All assuming that that the packages get updated at some sort of normal rate even if they lag behind the current version.)

In the case of sysinternals I could pin "--skip-virus-check" and "--ignore-checksums" and, like the situation above, can install the latest version of the program released by the developer without problems in the situation of I have a version installed, the package has been updated since my installation but the package is still not up to date and ignore all the virus warnings and refusal to install based on the believed virus count to be higher than the choco default threshold.

END RESULT:
Joy under specific conditions.

p..s I understand this could be done globally, but package specific granularity would be nice.

@bcurran3 bcurran3 changed the title FEATURE REQUEST: Support pinned install options FEATURE REQUEST: Support pinned package parameters per package (PPPPP) Jul 31, 2017
@ferventcoder ferventcoder added this to the 0.10.9 milestone Aug 6, 2017
@ferventcoder ferventcoder changed the title FEATURE REQUEST: Support pinned package parameters per package (PPPPP) Support pinned options per package Aug 6, 2017
@ferventcoder
Copy link
Member

This is quite similar to chocolatey/chocolatey-licensed-issues#11

@bcurran3
Copy link
Author

bcurran3 commented Aug 7, 2017

This is quite similar to chocolatey/chocolatey-licensed-issues#11

I don't see the relationship, but if it's on the roadmap to solve the problem via any method, I'm a happy camper.

@ferventcoder ferventcoder modified the milestones: 0.10.9, 0.10.10 Aug 29, 2017
@ferventcoder ferventcoder modified the milestones: 0.10.10, 0.10.12 Mar 27, 2018
@ferventcoder ferventcoder modified the milestones: 0.10.12, 0.10.13 May 3, 2018
@ferventcoder ferventcoder modified the milestones: 0.10.13, 0.10.14, 0.10.15 Mar 9, 2019
@ferventcoder ferventcoder modified the milestones: 0.10.15, 0.10.16 Apr 1, 2019
@gep13 gep13 modified the milestones: 0.10.16, 0.10.17 May 31, 2019
@ferventcoder ferventcoder modified the milestones: 0.10.17, 0.10.18 Jan 14, 2020
@ferventcoder ferventcoder modified the milestones: 0.10.18, 0.10.x Apr 14, 2021
@TheCakeIsNaOH
Copy link
Member

I think this should be solved by enabling remembered arguments once #1547 is implemented?

@gep13
Copy link
Member

gep13 commented Jan 30, 2023

I agree with @TheCakeIsNaOH assessment here. Going to go ahead and close this out.

If more discussion is needed, feel free to comment.

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

No branches or pull requests

4 participants