Support for 3rd party package managers about paket

[agross]

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.

[forki]

Actually we plan to support different package sources, but we didn't plan
which yet. Why do you think npm would be needed?
On Sep 7, 2014 2:19 PM, "Alexander Groß" [email protected] wrote:

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
http://www.hanselman.com/blog/IntroducingGulpGruntBowerAndNpmSupportForVisualStudio.aspx
.

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

[Horusiath]

@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.

[agross]

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.

Alex

Alexander Groß
Tiny phone, tiny mail

On Mon, Sep 8, 2014 at 9:27 PM, Bartosz Sypytkowski
[email protected] wrote:

@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.

Reply to this email directly or view it on GitHub:
#61 (comment)

[ilkerde]

My proposal ist to answer this question with No for the time being. @agross Move to FAQ and close?