Re^2: Pjam - continues integration for PERL, using pinto.

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;

Comment on Re^2: Pjam - continues integration for PERL, using pinto.

Replies are listed 'Best First'.
Re^3: Pjam - continues integration for PERL, using pinto. by Anonymous Monk on Dec 27, 2013 at 11:15 UTC
so what does pjam do that pinto by itself doesn't do already?	[reply]
Re^4: Pjam - continues integration for PERL, using pinto. by melezhik (Monk) on Dec 27, 2013 at 15:38 UTC
First of all, pinto itself it's just a tool to handle cpan-like repositories, it does nothing with HOW source code gets built and becomes distribution archives. So pjam is upper layer to integrate sources code changes (SCM) and pinto, which in turn produce builds (distribution archives). Right now it's only about subversion, but it can be generalized on other SCMs. Secondly, pjam is helpful abstraction to organize source code into structural projects to simplify distribution processes.	[reply]