Excerpts from brian d foy's message of Wed Jan 06 08:13:56 -0500 2010:
Is this in response to something in particular? Your message doesn't have any
threading headers, so I'm missing context.
hdp.
Excerpts from David Golden's message of Fri Oct 09 07:47:00 -0400 2009:
10. Add a free-text prerequisite field
Proposal:
Add free-text entries that *describe* prerequisites that cannot be
described right now, like prerequisite: a working libexpat, Need a perl
with defined-or, Need root
Excerpts from David Golden's message of Fri Oct 09 07:53:50 -0400 2009:
26. Specify a DLSIP resource
Proposal:
DLSIP codes should be specified in META.* as a resource.
My impression of DLSIP is that it's nearly as unused as the modules list. Is
this inaccurate?
hdp.
Excerpts from David Golden's message of Fri Oct 09 07:47:57 -0400 2009:
12. Allow Sequences (Arrays) for Prereqs
Proposal:
Right now, to the best of my knowledge, the only benefit of a the magic
Bundle:: namespace is that its prerequisites can be declared in optimal
installation order.
Excerpts from David Golden's message of Fri Oct 09 07:51:29 -0400 2009:
20. Make bugtracker resource a hash
Proposal:
The bugtracker resource shoudl be made into a hash that defines different
types of resources, e.g. web page, email report address, etc. (#toolchain
discussion)
Agree,
Excerpts from Graham Barr's message of Fri Oct 09 09:43:42 -0400 2009:
one option could be though that the failure for a recommended dependency to
install could still allow the dependent to install
On one hand, maybe this would be useful for things that e.g. offer a mod_perl
interface, and
Excerpts from David Golden's message of Fri Oct 09 09:59:22 -0400 2009:
I would like to specify in a usage section what is expected of
downstream parts of the toolchain.
This is probably a good idea for all the proposals.
hdp.
hello
hdp.
8 matches
Mail list logo
