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

paket update <package id> should be supported #239

Closed
agross opened this issue Oct 11, 2014 · 6 comments
Closed

paket update <package id> should be supported #239

agross opened this issue Oct 11, 2014 · 6 comments

Comments

@agross
Copy link
Contributor

agross commented Oct 11, 2014

E.g., to update just a single dependency.

@ilkerde
Copy link
Contributor

ilkerde commented Oct 12, 2014

👍

@forki
Copy link
Member

forki commented Oct 12, 2014

This is the idea:

  • load requirements from dependencies file
  • Add all pin requirements from lockfile (except for the package we want to
    update)
  • Run through resolver

Makes sense?
On Oct 12, 2014 12:04 PM, "ilkerde" [email protected] wrote:

[image: 👍]


Reply to this email directly or view it on GitHub
#239 (comment).

@ilkerde
Copy link
Contributor

ilkerde commented Oct 12, 2014

Makes great sense to me. Would enable even to have a specific list of packages to be updated.

@mexx
Copy link
Member

mexx commented Oct 12, 2014

How should this work with source file dependencies?

@forki
Copy link
Member

forki commented Oct 12, 2014

Good question.
On Oct 12, 2014 2:23 PM, "Max Malook" [email protected] wrote:

How should this work with source file dependencies?


Reply to this email directly or view it on GitHub
#239 (comment).

@forki
Copy link
Member

forki commented Oct 12, 2014

I think we should start with nuget packages.

I marked it up-for-grabs. I think it's not that hard.

I nobody volunteers I will do it next week.

@forki forki closed this as completed in ac34ee4 Oct 14, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants