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

Nuget vs Paket standardization #42

Open
tylerhartwig opened this issue Jul 14, 2019 · 1 comment
Open

Nuget vs Paket standardization #42

tylerhartwig opened this issue Jul 14, 2019 · 1 comment
Labels
bug Something isn't working question Further information is requested

Comments

@tylerhartwig
Copy link
Collaborator

Right now nuget packages are managed both through paket and nuget.

This causes issues for some packages (I ran into this with FSharp.Compiler.Service at runtime). FSharp.Compiler.Service needs to have proper constraints in the nuget package.

I'd like to make PR to standardize on either nuget or paket, and will also make the nuget constraint. Is there a preference towards either paket or nuget?
@tylerhartwig tylerhartwig added bug Something isn't working question Further information is requested labels Jul 14, 2019
@humhei
Copy link
Owner

humhei commented Jul 14, 2019 •
edited
Loading

I prefer nuget.
I have used paket before, but it troubled me sometimes because of weired problems (i forgetted the specific things as i have not used it for several months)

@humhei humhei mentioned this issue Jan 27, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working question Further information is requested
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@tylerhartwig @humhei