Re: Build and Installation of modules should be implementation specific (Was: Re: 6PAN Spec question)

2008-12-23 Thread Timothy S. Nelson
On Mon, 22 Dec 2008, Daniel Ruoso wrote: Em Seg, 2008-12-22 às 15:06 +1100, Timothy S. Nelson escreveu: On Sat, 20 Dec 2008, Mark Overmeer wrote: For ???B. In the current set-up, you use CPAN.pm to download, and then install. The 'cpan' script is a wrapper around CPAN.pm. CPAN.pm starts the

Build and Installation of modules should be implementation specific (Was: Re: 6PAN Spec question)

2008-12-22 Thread Daniel Ruoso
Em Seg, 2008-12-22 às 15:06 +1100, Timothy S. Nelson escreveu: > On Sat, 20 Dec 2008, Mark Overmeer wrote: > > For ???B. In the current set-up, you use CPAN.pm to download, and then > > install. The 'cpan' script is a wrapper around CPAN.pm. CPAN.pm starts > > the install tool. A more convient

Re: 6PAN Spec question

2008-12-21 Thread Timothy S. Nelson
On Sat, 20 Dec 2008, Mark Overmeer wrote: * Timothy S. Nelson (wayl...@wayland.id.au) [081220 03:45]: Btw, looks like I was wrong about the terminology of CPAN6/6PAN/whatever. See link below for details (the new Terminology section). http://svn.pugscode.org/pugs/docs/Perl6/Spec/S22-pa

Re: 6PAN Spec question

2008-12-20 Thread Mark Overmeer
* Timothy S. Nelson (wayl...@wayland.id.au) [081220 03:45]: > Btw, looks like I was wrong about the terminology of > CPAN6/6PAN/whatever. See link below for details (the new Terminology > section). > > http://svn.pugscode.org/pugs/docs/Perl6/Spec/S22-package-format.pod I do not understan

Re: 6PAN Spec question

2008-12-19 Thread Timothy S. Nelson
Btw, looks like I was wrong about the terminology of CPAN6/6PAN/whatever. See link below for details (the new Terminology section). http://svn.pugscode.org/pugs/docs/Perl6/Spec/S22-package-format.pod :) - | Name: T

Re: 6PAN Spec question

2008-12-18 Thread Timothy S. Nelson
On Fri, 19 Dec 2008, Timothy S. Nelson wrote: Are there any objections if I refactor the current S22 into 3 parts, and retain the .jib files stuff in the current S22 (renamed to S22-package-format.pod), a document containing "what S22 said about CPAN6" (which we could then donate to the cpan6

Re: 6PAN Spec question

2008-12-18 Thread Timothy S. Nelson
On Thu, 18 Dec 2008, Daniel Ruoso wrote: Em Qui, 2008-12-18 às 13:08 +1100, Timothy S. Nelson escreveu: My question is, what sort of information actually belongs in a final version of the 6PAN spec? I'm assuming it will at least include 6PAN Package format (layout, metadata, etc), and

CPAN6 vs. 6PAN (was: Re: 6PAN Spec question)

2008-12-18 Thread Timothy S. Nelson
Mark, am I right in putting it like this? 6PAN: - Perl6 package format - Client-side part of "CPAN" CPAN6: - Server-side part of "CPAN" (with more stuff) Is that how you see it? :) -

Re: 6PAN Spec question

2008-12-18 Thread Mark Overmeer
* jerry gay (jerry@gmail.com) [081218 14:01]: > > If you understand my explanation of CPAN6, then you certainly must be > > ware that 6PAN and CPAN6 have nothing to do with each other. Please do > > not use them in combination. It is as silly as saying TCP/Linux > there's a difference? that

Re: 6PAN Spec question

2008-12-18 Thread jerry gay
On Thu, Dec 18, 2008 at 05:45, Mark Overmeer wrote: > * Daniel Ruoso (dan...@ruoso.com) [081218 13:39]: >> Em Qui, 2008-12-18 às 13:08 +1100, Timothy S. Nelson escreveu: >> > My question is, what sort of information actually belongs in a final >> > version of the 6PAN spec? I'm assuming it wi

Re: 6PAN Spec question

2008-12-18 Thread Mark Overmeer
* Daniel Ruoso (dan...@ruoso.com) [081218 13:39]: > Em Qui, 2008-12-18 às 13:08 +1100, Timothy S. Nelson escreveu: > > My question is, what sort of information actually belongs in a final > > version of the 6PAN spec? I'm assuming it will at least include 6PAN > > Package > > format (layout

Re: 6PAN Spec question

2008-12-18 Thread Daniel Ruoso
Em Qui, 2008-12-18 às 13:08 +1100, Timothy S. Nelson escreveu: > My question is, what sort of information actually belongs in a final > version of the 6PAN spec? I'm assuming it will at least include 6PAN Package > format (layout, metadata, etc), and I'd suggest that it also include the >