On Fri, 29 May 2009, Jesse Vincent wrote:
> Making binary distribution easy is a laudable goal, but it's something
> the existing infrastructure already supports. I'd love to see "CPAN
> autobuilders" which build perl modules for a givven platform and
> architecture and make them generally availabl
On Sat, 30 May 2009, Mark Overmeer wrote:
* Timothy S. Nelson (wayl...@wayland.id.au) [090530 03:11]:
On Fri, 29 May 2009, Alex Elsayed wrote:
Instead, it would go to the distributions, who are already well-prepared to
handle packaging. We'd just be providing the tools and material they need
* Timothy S. Nelson (wayl...@wayland.id.au) [090530 03:11]:
> On Fri, 29 May 2009, Alex Elsayed wrote:
>> Instead, it would go to the distributions, who are already well-prepared to
>> handle packaging. We'd just be providing the tools and material they need to
>> do so.
>
> Let me reiterate that,
* Timothy S. Nelson (wayl...@wayland.id.au) [090530 02:15]:
>>> * PAUSE6; this is an actual network based on the CPAN6 software (see
>>> above). It also is not documented here.
>> Pause6 is one implementation of archive maintenance software. In the
>> first version written in Perl5, it implemen
> I support the notion of distributing binaries because nobody's gonna
> want to chew up their phone's battery doing unnecessary compiles. The
> ecology of computing devices is different from ten years ago.
And, in fact, binary distribution is something that's been done on CPAN
for quite a whil
On Fri, 29 May 2009, Alex Elsayed wrote:
IMO, that discussion should go in the direction of additional services:
the CPAN archive distributes what authors publish. The install tools
(CPAN.pm/CPANPLUS/successors) make that code fit in specific operating
systems. As a service, other people can pu
On Fri, 29 May 2009, Alex Elsayed wrote:
This problem strikes me as intractable - I think the only thing we can do is
provide a dependency specifier, clearly tagged as being external to the CPAN 6
archive, with a sensible name that allows a human to intervene and find the
correct package for the
On Fri, 29 May 2009, Daniel Ruoso wrote:
So, I'd expect to have a Debian archive, in the Debian case, hosted by
the Debian Perl group (which packages about ~ 500 CPAN modules to Debian
today) with the binary packages targetting each of the Debian
versions...
The same would go for RedHat and oth
> I know that Rakudo is not the official implementation. The problem is
> that you misunderstood my post. I did not say to distribute PIR to the
> exclusion of Perl source. You know that I was replying to Larry's
> comment that he supported the notion of distributing binaries. Surely
> you didn't t
On Fri, 29 May 2009, Mark Overmeer wrote:
* PAUSE6; this is an actual network based on the CPAN6 software (see
above). It also is not documented here.
Pause6 is one implementation of archive maintenance software. In the
first version written in Perl5, it implements things like
I'
> I believe he is arguing that whatever we end up doing needs to make it
> easy for an external package-manager to find out what files CPAN6.pm
> is going to install, and where, and what the dependencies were (both
> Perl and system libraries). So that the various distributions can
> make native p
On Friday 29 May 2009 1:51:40 am Mark Overmeer wrote:
> I would really like to see a split in terminology being used for the
> various seperate problems. The traditional confusion about what CPAN is:
> an archive or an install tool. Package manager discussions are in the
> process AFTER the insta
On Fri, May 29, 2009 at 10:02:20PM +1000, Timothy S. Nelson wrote:
> On Fri, 29 May 2009, Mark Overmeer wrote:
>> IMO, that discussion should go in the direction of additional services:
>> the CPAN archive distributes what authors publish. The install tools
>> (CPAN.pm/CPANPLUS/successors) make th
While lurking in IRC, I've seen several discussions of what CPAN 6 should
look like. Honestly, wayland76++'s idea for packaging seems the best to me.
Most of the suggestions so far, especially those based on alien, apt, yum,
or other existing package managers have a few major problems:
* Alien
Em Sex, 2009-05-29 às 01:54 +0200, Daniel Carrera escreveu:
> Larry Wall wrote:
> > I support the notion of distributing binaries because nobody's gonna
> > want to chew up their phone's battery doing unnecessary compiles. The
> > ecology of computing devices is different from ten years ago.
> By
* Timothy S. Nelson (wayl...@wayland.id.au) [090529 12:02]:
> On Fri, 29 May 2009, Mark Overmeer wrote:
> * CPAN6; this is a piece of software for managing an archive network (such as
> Pause6, below). This is not specified in this document; see
> http://cpan6.org/
Yes. It facilitates organi
On Fri, 29 May 2009, Mark Overmeer wrote:
* Alex Elsayed (eternal...@gmail.com) [090528 22:17]:
While lurking in IRC, I've seen several discussions of what CPAN 6 should
look like.
I would really like to see a split in terminology being used for the
various seperate problems. The traditional
On Fri, 29 May 2009, Daniel Carrera wrote:
Timothy S. Nelson wrote:
I can confirm that Redhat supports multiple versions:
$ rpm -q kernel
kernel-2.6.27.5-117.fc10.i686
kernel-2.6.27.12-170.2.5.fc10.i686
kernel-2.6.27.5-117.local.fc10.i686
AFAIK the way RPM implements "multiple versions"
* Alex Elsayed (eternal...@gmail.com) [090528 22:17]:
> While lurking in IRC, I've seen several discussions of what CPAN 6 should
> look like.
I would really like to see a split in terminology being used for the
various seperate problems. The traditional confusion about what CPAN is:
an archive
Timothy S. Nelson wrote:
I can confirm that Redhat supports multiple versions:
$ rpm -q kernel
kernel-2.6.27.5-117.fc10.i686
kernel-2.6.27.12-170.2.5.fc10.i686
kernel-2.6.27.5-117.local.fc10.i686
AFAIK the way RPM implements "multiple versions" is by making an
entirely different package.
Alex Elsayed wrote:
On Thursday 28 May 2009 4:54:50 pm Daniel Carrera wrote:
On the other hand, distributing Parrot bytecode (or PIR, or PASM) seems
fine. But I don't know what to suggest for modules that require a C
compiler.
The problem with that is that Rakudo isn't the "Official" impelentati
On Thu, 28 May 2009, Alex Elsayed wrote:
On Thursday 28 May 2009 4:04:28 pm Daniel Carrera wrote:
At first I liked wayland76's proposal, but now I have a new concern:
Most package managers are not designed to hold multiple versions of the
same package. As indicated in S11, it is important that
On Thursday 28 May 2009 4:54:50 pm Daniel Carrera wrote:
> On the other hand, distributing Parrot bytecode (or PIR, or PASM) seems
> fine. But I don't know what to suggest for modules that require a C
> compiler.
The problem with that is that Rakudo isn't the "Official" impelentation, and
never wi
Larry Wall wrote:
I support the notion of distributing binaries because nobody's gonna
want to chew up their phone's battery doing unnecessary compiles. The
ecology of computing devices is different from ten years ago.
By binaries, I assume you mean native binaries, as opposed to Parrot
bytec
On Thursday 28 May 2009 4:22:00 pm Larry Wall wrote:
> I support the notion of distributing binaries because nobody's gonna
> want to chew up their phone's battery doing unnecessary compiles. The
> ecology of computing devices is different from ten years ago.
I agree. My ideal situation would be t
On Thursday 28 May 2009 4:04:28 pm Daniel Carrera wrote:
> * We were mainly looking at Alien as a source of Perl code we could borrow.
Ah, I was lumping it in with the previous proposals to actually use .deb as
the official P6 package format. My mistake.
> * The point of wayland76's proposal was
On Fri, May 29, 2009 at 01:04:28AM +0200, Daniel Carrera wrote:
> Hi Alex,
>
> I hve comments.
>
> Alex Elsayed wrote:
>> While lurking in IRC, I've seen several discussions of what CPAN 6
>> should look like. Honestly, wayland76++'s idea for packaging seems the
>> best to me. Most of the suggest
Hi Alex,
I hve comments.
Alex Elsayed wrote:
While lurking in IRC, I've seen several discussions of what CPAN 6 should
look like. Honestly, wayland76++'s idea for packaging seems the best to me.
Most of the suggestions so far, especially those based on alien, apt, yum,
or other existing packa
While lurking in IRC, I've seen several discussions of what CPAN 6 should
look like. Honestly, wayland76++'s idea for packaging seems the best to me.
Most of the suggestions so far, especially those based on alien, apt, yum,
or other existing package managers have a few major problems:
* Alien
29 matches
Mail list logo
