comment on

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

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Problems? Is your data what you think it is?
	PerlMonks