Methods for PIP and NPM about cuisine HOT 17 CLOSED

I wrote a function to install pip packages. I can commit it if people are interested. It's pretty simple right now.

from cuisine.

I also got a set of methods to install these packages and I think this is something alot of people use - so I'm wondering if this is something that should be part of Cuisine's core or it should be seperate project

from cuisine.

In Puppet for example there's no support for this stuff in the core

from cuisine.

@gudbergur @josephmc5 It would be great to have PIP/NPM and any other type of specific package installation method. What I suggest is to name the functions this way:

package_python_pip_*
package_node_npm_*

You can past the code in this issue and I'll integrate it, or send me a patch.

from cuisine.

i have written the code for pip and easy_install with install, upgrade, ensure, remove functions. i am happy to provide that code.
just encountered one issue during testing: depending on the system setup you might need to run these with sudo and will not be able to run without, or you do not have sudo rights and will get an error otherwise.
so either we use the mode_sudo, mode_user etc, or we run run without and catch the permission denied and then if errored, run again with sudo. any preferences

from cuisine.

Could you share a gist with the code? thanks!

from cuisine.

please finde the code here: https://gist.github.com/1950506
@sebastien this code is equivalent to the diff file that i send to you

from cuisine.

Is this issue closed?

I want to write some codes for pip install and some feature of Cuisine.
If these feature is not implemented yet, I would add this feature to Cuisine.

And I'm thinking about virtualenv generator.
This cookbook (https://github.com/opscode-cookbooks/python) is awesome for Python environment.
I will convert these feature for Cuisine.

How about it?

from cuisine.

I wrote an example code for this issue.

https://gist.github.com/3096986

from cuisine.

i am not sure, if you follow the syntax/naming convention that sebastien had in mind (at least I had a different understanding as you can see in my gist https://gist.github.com/1950506, but I think @sebastien needs to make the call here.

from cuisine.

I think the best would be to name the functions pip_package_{install|ensure|update|remove} (and conversely easyinstall_{install|ensure|update|remove} and use the @dispatch decorator.

@schacki sorry for not having integrated this yet, but I haven't found the time to test it yet.
@wutali maybe you could merge both @schacki's code and yours, clean it up and submit a pull request?

from cuisine.

@sebastien OK! I will clean up @schacki and my code.

By the way, I want to add virtualenv and some useful feature for Python.
Should this feature be separated another project or main cuisine project?

from cuisine.

@wutali the best would be to put the virtualenv and python-specific functions in a separate module, to keep cuisine small -- but you can let me know and maybe some functions would be useful for cuisine's core.

from cuisine.

@Sebastion: you had the idea to have some kind of contrib folder,where such
things could be stored?!

On Friday, July 13, 2012, Sébastien Pierre wrote:

@wutali the best would be to put the virtualenv and python-specific
functions in a separate module, to keep cuisine small -- but you can let me
know and maybe some functions would be useful for cuisine's core.

---

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

from cuisine.

Yes, exactly -- provided the modules have a clear purpose and are generic enough.

from cuisine.

hi sebastien, i am planning to use such kind of code again, will you integrate it any time soon, or do i need to include it in my deployment scripts?

from cuisine.

I'm closing the issue as the @dispatch mechanism would support that.

from cuisine.