f perl applications distribution archives from source code.

What is that exactly? The github doesn't explain

... gem install pjam ...

fantastic :D

... gem install pjam ...

LOL. Just you wait. Soon enough some bright young dev will get tired of Makefiles and decide that Ruby should build with CMake or Jam.

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"
[download]

I don't understand why anyone except the author would ever use pjam

well pinto doc well explained this : An "archive" is the file that developers ship, which contains all their application/library code, test cases, build scripts etc. Conversely, the archive is the file that users must fetch to install the application/library. Sometimes I also refer to these as "distributions".

so perl applications distribution archives are just archive to be unpacked and installed on target host, to run a PERL application

gem install pjam -- fantastic :D /// why not? :) I used to code on PERL for about 10 yeas, then I switched to ruby, but my daily job is to install perl applications; So I wrote pjam using ruby; but for end users it's just a tool that works;

so what does pjam do that pinto by itself doesn't do already?

... from source code; - forgot to clear this; Pjam automates creation of distribution archive from source code check out from SCM ( currently svn ) - an so may be utilize in CI processes