Re: Commentary on S22 (CPAN [DRAFT])

2009-05-30 Thread jesse



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 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 directory called 
META-INF.  There's no particular technical reason to pick a given
name, so going for something that looks familiar to people may be a win.

-jesse


Re: Commentary on S22 (CPAN [DRAFT])

2009-05-30 Thread Daniel Carrera

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 directory called 
META-INF.  There's no particular technical reason to pick a given

name, so going for something that looks familiar to people may be a win.


Sounds reasonable. Like you said, there is no strong reason to pick one 
name or another, so why not pick the name everyone else already uses?


Daniel.


Re: Commentary on S22 (CPAN [DRAFT])

2009-05-29 Thread Daniel Carrera

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 --armor 
(.asc extension).


To expand on this idea: The current JIB spec includes an Author field in 
META.info. The spec says:


- Author CPAN author id


This is perfect. We can offer that people create a CPAN id before 
distributing apps in PAR format, and upload their GPG public key. Then, 
when the user installs the app, the installer downloads the public key 
from CPAN and checks the signature.


Of course, we can't mandate that people register with CPAN. This is just 
a service. So there should be an option to check a signature using a 
public key you got from elsewhere, or to disable the signature check 
entirely.


Daniel.