-
Notifications
You must be signed in to change notification settings - Fork 520
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 for 3rd party package managers #61
Comments
Hm, I don't see a point in replicating bower and npm, especially given that they appear to have the same features as Paket (e.g. pessimistic version constraints). Why not just use them when you want to install "their" packages? VS.next does the same. |
Actually we plan to support different package sources, but we didn't plan
|
@forki npm came to my mind, since it has an excellent support for client side MV* frameworks, especially AngularJS - for example yeoman scaffold generators (and yeoman itself) as well as both testing runtimes Karma and Protractor are distributed as npm packages. @agross From my point of view Paket could be potentially used as abstraction layer above various package managers - one manager to rule them all. If it only purpose was to fix NuGet, then simple fork (NuGet++) would be a better solution. |
Hm, I don't see a point in reinventing other wheels. One to rule them all would likely result in an abstraction that's less usable and flexible than the things we're trying abstract in the first place. AlexAlexander Groß On Mon, Sep 8, 2014 at 9:27 PM, Bartosz Sypytkowski
|
My proposal ist to answer this question with No for the time being. @agross Move to FAQ and close? |
I've noticed that Packet offers a lot nicer and more useful way do manage project dependencies than what NuGet provides, I would like to be able to use it with other package managers.
Example: When you want to provide support web-oriented projects with many client-side libraries, you may still rely on NuGet, but from my own experience bower and npm are much richer in this matter.
So my question is - are you guys thinking about providing layer for third party package managers?
The text was updated successfully, but these errors were encountered: