On Mon, Dec 05, 2011 at 06:21:13PM -0600, brian d foy wrote:
In article 20111205154758.gh17...@bytemark.barnyard.co.uk, David
Cantrell da...@cantrell.org.uk wrote:
There's at least one other significant difference: CPAN has an
up-to-date index. BackPAN doesn't.
Well, CPAN's index is also
On Tue, Dec 6, 2011 at 7:32 AM, David Cantrell da...@cantrell.org.uk wrote:
On Mon, Dec 05, 2011 at 06:21:13PM -0600, brian d foy wrote:
In article 20111205154758.gh17...@bytemark.barnyard.co.uk, David
Cantrell da...@cantrell.org.uk wrote:
There's at least one other significant difference:
On Fri, Dec 02, 2011 at 10:41:29PM -0800, Jeffrey Thalhammer wrote:
On Dec 2, 2011, at 7:10 PM, Michael G Schwern wrote:
You might want to record the type of repository, even if there's
only CPAN for now. It might be worth differentiating CPAN from
BackPAN.
The structure is the same,
On Mon, Dec 5, 2011 at 10:47 AM, David Cantrell da...@cantrell.org.uk wrote:
There's at least one other significant difference: CPAN has an
up-to-date index. BackPAN doesn't.
Further to that point, I think the idea of the index should be
separated from the idea of the repository.
The
David Golden xda...@gmail.com writes:
I plan to expand further on this idea of separation at the QA
Hackathon in the spring (if I don't start working on it sooner). I'd
like to get all CPAN clients able to use an index completely separate
from a given repository, where the index could, for
David Golden xda...@gmail.com writes:
I plan to expand further on this idea of separation at the QA
Hackathon in the spring (if I don't start working on it sooner). I'd
like to get all CPAN clients able to use an index completely separate
from a given repository, where the index could,
On 12/05/2011 11:05 AM, David Golden wrote:
Among other things, this would allow a project to freeze (and version
control) a CPAN index and use it for repeatable deployment of a
specific dependency chain.
Isn't this what carton is trying to do?
https://github.com/miyagawa/carton
--
Michael
In article 20111205154758.gh17...@bytemark.barnyard.co.uk, David
Cantrell da...@cantrell.org.uk wrote:
There's at least one other significant difference: CPAN has an
up-to-date index. BackPAN doesn't.
Well, CPAN's index is also BackPAN's index. That is, neither of them
include all of the
On Mon, Dec 5, 2011 at 6:37 PM, Michael Peters mpet...@plusthree.com wrote:
Among other things, this would allow a project to freeze (and version
control) a CPAN index and use it for repeatable deployment of a
specific dependency chain.
Isn't this what carton is trying to do?
On Mon, Dec 5, 2011 at 6:27 PM, Ricardo Signes perl...@rjbs.manxome.org wrote:
We have a tool to do this, at work. It isn't really in a state that I'd
suggest others use it, but I would love to see something better than it become
popular, as it has been *very* useful. So, I will be happy to
On Dec 2, 2011, at 7:48 PM, David Golden wrote:
I would encourage you to use existing names/conventions whenever
possible. Some references to consider if you haven't.
Thanks for reminding me about your blog post on the subject -- I had forgotten
about that. And I read some other
You might want to crib from BackPAN::Index. It has a lot of this terminology.
On 2011.12.2 5:21 PM, Jeffrey Thalhammer wrote:
The context is Pinto, which is yet-another suite of libraries and tools
for building a private CPAN-like repository.
Does it explode when hit from the rear? No?
On Fri, Dec 2, 2011 at 8:21 PM, Jeffrey Thalhammer
j...@imaginative-software.com wrote:
Hi everyone-
I need some suggestions for terminology to use in my code and documentation.
I'm picky about names, so this is important to me (perhaps more than it
should be). The context is Pinto, which
# from Michael G Schwern
# on Friday 02 December 2011 19:10:
Module: I actually avoid using the term Module because I think it is
often misused. I feel that a Module is a physical file (i.e.
something that you use). But some folks use the terms Module and
Package interchangeably. To be
On Dec 2, 2011, at 7:10 PM, Michael G Schwern wrote:
Distribution: A Distribution is an abstract concept that defines
relationships between packages. The minimal concrete implementation
of a Distribution would be just a META.json (or equivalent) file.
Distributions also have names and
15 matches
Mail list logo
