On Thu, Apr 01, 2010 at 12:39:27AM -0400, David Nicol wrote:
On Wed, Mar 31, 2010 at 7:43 AM, Ask Bjørn Hansen a...@perl.org wrote:
The main point here is that we can't use 20 inodes per distribution.
so don't. How much reengineering would be needed to keep CPAN in a
database instead of a
-Original Message-
From: Tim Bunce [mailto:tim.bu...@gmail.com] On Behalf Of Tim Bunce
Sent: Thursday, April 01, 2010 5:51 PM
To: cpan-workers; module-authors@perl.org
Subject: Distributing the CPAN
* cpanminus already supports installing from a git repo.
* Over time the number
On Wed, 31 Mar 2010, Ask Bj?rn Hansen wrote:
snip
Everyone who doesn't run mirrors says oh, who cares - it doesn't bother me.
Some of us who does run mirrors say actually, that sort of thing is important and
an actual issue..
Others reply then you're doing it wrong. But nobody came with
On Apr 1, 2010, at 1:12 PM, Tim Bunce wrote:
Yes, I was envisaging something like gitPAN. Though if this took off
then moving the tarball-git import logic to the PAUSE server would
probably be a good idea.
/me stashes these ideas away for PGAN…
On Fri, 2 Apr 2010, Ask Bj?rn Hansen wrote:
I can't believe I'm doing this, but ...
:-) All for entertainment's sake...
The main point here is that we can't use 20 inodes per distribution. It's Just
Nuts. Sure, it's only something like 400k files/inodes now - but at the rate
it's going
On Fri, 2 Apr 2010, Ask Bj?rn Hansen wrote:
Talk = ZzZz.
Code = Interesting.
Deployment = Useful.
Please. The talk serves to gauge interest before I waste any time
implementing a solution that's already been rejected out of hand. As I've
mentioned repeatedly I already use rsync, albeit on
