jesse wrote:
1) Instead of calling the format "JIB", how about "PAR"? It can stand
for Perl ARchive or the recursive PAR ARchive. This is more memorable.
It might make sense to adopt the same naming as .jar and .epub, two very
different zipfile-as-container formats. Both use a top-level directo
On Fri, May 29, 2009 at 11:04:38PM +0200, Daniel Carrera wrote:
> Hello,
>
> I finished reading S22 (CPAN [DRAFT]). This synopsis is about the
> package format, not about the network. I have some comments:
>
> 1) Instead of calling the format "JIB", how about "PAR"? It can stand
> for Perl A
Daniel Carrera wrote:
4) Lastly, while we are at it, why don't we add a signature file to the
_par directory?
_par/
META.info
CHECKSUMS.asc
The CHECKSUMS.asc file would contain the SHA1 sums of every file in the
archive except for itself. The file could be GPG-signed with
Hello,
I finished reading S22 (CPAN [DRAFT]). This synopsis is about the
package format, not about the network. I have some comments:
1) Instead of calling the format "JIB", how about "PAR"? It can stand
for Perl ARchive or the recursive PAR ARchive. This is more memorable.
2) S22 proposes
