in reply to Re^2: Pjam - continues integration for PERL, using pinto.
in thread Pjam - continues integration for PERL, using pinto.

so what does pjam do that pinto by itself doesn't do already?
  • Comment on Re^3: Pjam - continues integration for PERL, using pinto.

Replies are listed 'Best First'.
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.