On 3/5/07, brian d foy <[EMAIL PROTECTED]> wrote:
In article <[EMAIL PROTECTED]>, Ricardo
SIGNES <[EMAIL PROTECTED]> wrote:
> * brian d foy <[EMAIL PROTECTED]> [2007-03-04T12:09:26]
> > I'm not talking about the particular field name, but the idea that I'd
> > want to say in META.yml "Don't send me mail", or whatever setting I
> > want.
> >
> > Instead of having to disable (or enable) CC for every new tool, I'd
> > want a setting that new tools could look at without me having to change
> > the META.yml in all of my distributions then re-uploading them all.
> So, for some subset of META.yml settings, you could consult the module's
> author
> settings, found at (say) $MIRROR/authors/.../RJBS/METAMETA.yml
> Something like that? I feel a potentially irrational sense of dread.
I'm not even sure what you mean by that, and it certainly isn't
anything I'm talking about.
I'm just saying that setting configuration options per tool isn't the
way to handle global preferences.
That's why my first suggestion was
hints:
test_reporter:
cc_author: "whatever makes sense like 0 or the map suggested by
David Golden or both"
It means the author is giving some hints. In the specific case, they
are hints for a test reporter which has some news to tell about a test
run of some of the author's distributions. The author is saying in
which conditions he would like to receive a cc-ed copy of the test
report. Of course, CPAN::Reporter got the lead because it is one of
the first modules which integrated to CPAN to do this reporting stuff.
So it is fair, it defines the meaning of attributes like cc_author.
Nevertheless, it is a global preference. Other test reporters could be
given hints with the same part of META.yml
I don't think it is hard to see that other tools may take advantage of
hints provided by authors as well.
