CPAN::Reporter::Smoker::Installed?

But I'm terrible at names.  Other people always suggest better ones after I
release something to CPAN.  ;-)

-- David

On Sun, Jan 18, 2009 at 9:01 PM, David Westbrook <dwestbr...@gmail.com>wrote:

> thanks for the comments!
>
> Any suggestions for a good CPAN::Reporter::Smoker::* subclass name?
>
> --david
>
> On Sun, Jan 18, 2009 at 8:31 PM, David Golden <xda...@gmail.com> wrote:
> > On Sun, Jan 18, 2009 at 7:59 PM, David Westbrook <dwestbr...@gmail.com>
> > wrote:
> >>
> >> Whereas you wouldn't want to run a smoker on a "regular" machine (e.g.
> >> a $work box, or your day-to-day windows desktop, or laptop, etc),
> >> this is reasonably safe since it's only testing distros that you
> >> already installed, which implies that they (and their dependencies)
> >> are trusted.
> >> Also lets you easily submit reports for all the modules you're actual
> >> using, w/o a separate smoke environment.
> >
> > I like it.  Among other things, it could be used with the File transport
> to
> > save reports to a directory for examination, which could be useful to
> check
> > things before upgrading.
> >
> >>
> >>  Is this useful for others?
> >>    If so, as a snippet (e.g. posted on wiki)?
> >>    as a subclass (name??) of CPAN::Reporter::Smoker?
> >>    as an additional exported sub (name??) in CPAN::Reporter::Smoker?
> >
> > At the very least, I'd put it on the CPAN Testers wiki.  I have no
> problem
> > if you want to publish a CPAN::Reporter::Smoker::* module, but I don't
> think
> > I want to include it in C::R::Smoker itself, mostly because it's a
> slipperly
> > slope of extra maintenance work for me if I start accepting different
> ways
> > of generating the list.
> >
> > -- David
> >
> >
>

Reply via email to