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
pinto pull <github_url> #99
Comments
If you want to build dependencies straight from a Git repository, then I think a setup with Pinto only deals with packaged distributions (i.e. tar.gz files). However, you could (should) wire up a continuous integration system that builds, tests, and packages your forked repositories on every commit. Then you can automatically ship those packages to Pinto. @melezhik has been working on I'll leave this issue open to remind me about your use case. Maybe I'll think of something. But for now, I don't see this in the near future for Pinto. |
yes, recently I renamed it to pjam :)) ... and I also think that SCM and pinto integration should be done somewhere else, not in pinto - to not complicated the things ... Right now pjam only integrate subversion based projects and pinto, but if it's demanded I may think about git too ... feel free to check out pjam project - introduction may be found there ... |
@thaljef There are github repos such as vti/Twiggy, which is a forked & modified version of the original CPAN one. It's necessary for anyone wanting to use SockJS on their webserver. It would be fun if we could "pinto pull" vti/Twiggy quickly and easilly, that's all I'm saying. |
this will be supported in Carton 1.1 by appending git URL to |
I agree. Just not sure how to make it work for Pinto. Here's what I would like to see happen though: @vti releases his version of Twiggy to his repository on Stratopan, and then you can pull it into your own repository (also on Stratopan or elsewhere). |
Often I don't want to use a module from CPAN, but rather a module I (or somebody else) forked from Github and edited.
Such is the case with DJabberd, which I'll be forking and maintaining on a github repository.
I think in this case, without the command
pinto pull <github_url>
, life would be hard (every edit I make would require me to create a tgz and feed it to pinto). With the command (if I'm allowed to repeatedly invoke it, even with no bump in the version number), life would get easy.The text was updated successfully, but these errors were encountered: