I really don't understand the purpose behind pjam -- its like a shell script I coded myself to remember pinto ... perl Build.PL && ./Build dist
something like milla/minilla except written in ruby with giant if/else block
I wouldn't trust this style of coding 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 di
+st --quiet 1>/dev/null && ln -fs `ls #{project_id}/#{config['applicat
+ion']}/*.gz` #{project_id}/current.tar.gz && echo -n `ls *.gz` > #{pr
+oject_id}/current.txt"
I don't understand why anyone except the author would ever use pjam | [reply] [Watch: Dir/Any] [d/l] [select] |
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 --q
+uiet 2>/dev/null 1>/dev/null && ./Build dist --quiet 1>/dev/null"
Hopefully you don't have any important zipped files lying around in that directory. And hopefully nothing anywhere near this script involves shell metacharacters, because this guy has never heard of escaping. An amateur implementation of a pointless idea -- all too common in Ruby. | [reply] [Watch: Dir/Any] [d/l] |
I really don't understand the purpose ... - If to say about pjam purposes please read my previous comment
I wouldn't trust this style of coding - really, you don't have to (:, it *just works for me*, and I wrote in documentation *WHEN it may works for others* ... and ... don't take implementation too serious, one day I may re-factoring this. I know code may look ugly, but again *it just works for me*, it's prototype, but I use it on my day to day basis and this make life easier , so why I can't share this with others, we call it open source, don't we?
| [reply] [Watch: Dir/Any] |
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" :)
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.
| [reply] [Watch: Dir/Any] [d/l] |