-
Notifications
You must be signed in to change notification settings - Fork 525
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 pack: need a way to specify current nuget version as dependency #837
Comments
Mhm good question. @mavnn do you have a suggestion how we could implement such a feature? |
@eiriktsarpalis how would you like to configure this feature. I think I can add it easily, but we need to define where and how. |
I could think if two possible ways: either use a macro in the template
|
I think it should be done in the template. |
I tend to agree, it would make package definitions more self contained.
|
do you already started the conversion? I'd love to use it as a sample to implement this. |
Yeah, I started an effort in this branch, though I never completed it. |
I'm getting the following error while trying to pack that FsPickler branch with 1.9.0:
|
thx. I found this bug and fixed it in 1.9.1. |
Thanks, seems to be working now. |
I'm interested in integrating the
paket pack
functionality in my projects, so I've started playing around with it in FsPickler. In FsPickler there are two projects, FsPickler and FsPickler.Json. FsPickler has no nuget dependencies and FsPickler.Json depends on 1) Json.Net and 2) FsPickler of precisely the same version number.I can rely on the Json.Net dependency being added automatically by
paket pack
, however I can't find a way to specify the latter dependency correctly. Is there any way I can achieve this through thepaket.template
syntax or FAKE?The text was updated successfully, but these errors were encountered: