Right now it's only about subversion, but it can be generalized on other SCMs.

Sure it can, if you start from scratch ... giant if/else trees don't lend to extension very well or collaboration ... they're not plugins

Also I wouldn't call svn log && svn up "scm integration" :)

cmd = "cd #{project_id}/#{src}
&&  svn log -r BASE:HEAD --verbose . > dry-run.log"

cmd ="pinto #{repo_root} pull -s #{config['stack']} -v #{wd_flag} --us
+e-default-message #{m} #{color_flag}"

cmd = "cd #{project_id}/#{src}
&& rm -rf cpanlib
&& svn up "cmd = "export version_postfix='#{version_postfix}'
&& cd #{project_id}/#{src}
&& rm -rf *.gz
&& rm -rf MANIFEST
&& perl Build.PL --quiet 1>/dev/null 2>module_build.err.log 
&& ./Build realclean
&& perl Build.PL --quiet 1>/dev/null 2>module_build.err.log
&& ./Build manifest --quiet 2>/dev/null 1>/dev/null 
&& ./Build dist --quiet 1>/dev/null"

cmd ="cd #{project_id}/#{src}
&& pinto #{repo_root} delete -v PINTO/#{distro_name} #{color_flag}"

cmd ="cd #{project_id}/#{src}
&& pinto #{repo_root} add  -s #{config['stack']} -v #{wd_flag} --use-d
+efault-message #{distro_name} #{color_flag}"

cmd = "pinto #{repo_root} list -s #{config['stack']} --format %a/%f  -
+-no-color | sort | uniq > #{project_id}/packages.txt"

cmd = "#{env_string}
&& pinto #{repo_root} install -s #{config['stack']} -l #{local_lib} -o
+ 'q' #{m} #{color_flag}"

cmd = "#{env_string}
&& pinto #{repo_root} install -s #{config['stack']} -l #{local_lib} -o
+ 'q' PINTO/#{d} #{color_flag}"

cmd = "export version_postfix='#{version_postfix}'
&& cd #{project_id}/#{config['application']}
&& rm -rf cpanlib
&& mkdir cpanlib/
&& cp -r #{local_lib}/* cpanlib/
&& rm -rf *.gz
&& ./Build realclean --quiet 1>/dev/null
&& perl Build.PL --quiet 1>/dev/null 2>module_build.err.log
&& ./Build manifest --quiet 2>/dev/null 1>/dev/null
&& ./Build dist --quiet 1>/dev/null
&& ln -fs `ls #{project_id}/#{config['application']}/*.gz` #{project_i
+d}/current.tar.gz
&& echo -n `ls *.gz` > #{project_id}/current.txt"

cmd = "cd #{project_id}
&& #{env_string}
&& pinto #{repo_root} install -s #{config['stack']} -l #{local_lib} -o
+ 'test-only' PINTO/`cat current.txt` #{color_flag}"

[download]

so why I can't share this with others, we call it open source, don't we?

You can share it , you already did :) Now you say "i made this, works for me" , and that is fantastic,

now others get to decide if they should choose pjam based on criteria that is important to them

Your descriptions of what pjam did sounded so wonderously buzz-wordy I had to look at the source to see what it does. Now that I've seen, no thanks.

In reply to Re^5: Pjam - continues integration for PERL, using pinto. by Anonymous Monk
in thread Pjam - continues integration for PERL, using pinto. by melezhik

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.