In article [EMAIL PROTECTED], A. Pagaltzis
[EMAIL PROTECTED] wrote:
* _brian_d_foy [EMAIL PROTECTED] [2005-08-22 20:00]:
Sure, but you and brian arenât the kind of people whoâd need h2xs
or module-starter or the like anyway. I find it kind of strange
to be telling people without enough
What do you think about Module::Starter also building, by default, a
test file that checks for the boilerplate text?
Now *that* is a great idea!
Robert Rothenberg wrote:
What do you think about Module::Starter also building, by default, a
test file that checks for the boilerplate text?
Now *that* is a great idea!
And while they're at it, they can add test files for Test::Pod,
Test::Pod::Coverage, Test::Distribution, Test::Fixme,
* David Golden [EMAIL PROTECTED] [2005-08-23 13:00]:
And while they're at it, they can add test files for Test::Pod,
Test::Pod::Coverage, Test::Distribution, Test::Fixme,
Test::PerlTidy, Test::Prereq, Test::Spelling, and
Test::Signature, and then release the whole thing as
A. Pagaltzis wrote:
* Robert Rothenberg [EMAIL PROTECTED] [2005-08-21 13:40]:
No matter what wiz-bang new module starter system somebody
comes up with, there will be some kind of boilerplate text.
Unless maybe it asks you to write the documentation before you
write the module.
Maybe the
Title: RE: RFC - Test::Stupid module
there will be some kind of boilerplate text. Unless maybe it
asks you to write the documentation before you write the module.
(Fine for some developers, but not everyone.)
Now that would be a cool tool. You simply write a bunch of .t files
Selon David Landgren [EMAIL PROTECTED]:
Or have Module::Starter know how to include site-local boilerplate. I
like addnig a fixed blurb on how to report bugs (and no doubt other
stuff but that's what I can think of without looking). If M::S knew how
to fetch that during a run it would save me
* Robert Rothenberg [EMAIL PROTECTED] [2005-08-20T18:58:25]
The problem is that authors use boilerplates. With Module::Starter there
are lots of modules with abstracts The great new [modulename]. No
matter what wiz-bang new module starter system somebody comes up with,
there will be some
David Landgren wrote:
Or have Module::Starter know how to include site-local boilerplate. I
like addnig a fixed blurb on how to report bugs (and no doubt other
stuff but that's what I can think of without looking). If M::S knew how
to fetch that during a run it would save me from having to
On Mon, Aug 22, 2005 at 10:30:01AM +0200, David Landgren ([EMAIL PROTECTED])
wrote:
Or have Module::Starter know how to include site-local boilerplate. I
It does. Plugins.
--
Andy Lester = [EMAIL PROTECTED] = www.petdance.com = AIM:petdance
On Aug 19, 2005, at 9:51 AM, Andy Lester wrote:
On Fri, Aug 19, 2005 at 07:40:10AM -0700, David Baird
([EMAIL PROTECTED]) wrote:
Sure, but the point remains, perhaps better stated as make it really
easy for the really lazy, including me. I'm all in favour of modules
that help *me* not make an
In article [EMAIL PROTECTED], A. Pagaltzis
[EMAIL PROTECTED] wrote:
* _brian_d_foy [EMAIL PROTECTED] [2005-08-20 23:15]:
When you want to add something (like a standard test file), you
just add it to the sample dist. When you want to change some
boilerplate, you just change it in the
--- _brian_d_foy [EMAIL PROTECTED] wrote:
In article [EMAIL PROTECTED], A. Pagaltzis
[EMAIL PROTECTED] wrote:
Using a tool from CPAN is not conceptually different from what
youâre doing, but a good way for developers who havenât
developed
specific needs and wants (yet) to get a
* _brian_d_foy [EMAIL PROTECTED] [2005-08-22 20:00]:
It is completely different. A tool from CPAN is somebody else's
idea of what your module distro should look like. Mine, not
being a module starter tool, is your own idea. It doesn't know
anything about modules other than what you tell it.
The problem is that authors use boilerplates. With Module::Starter there
are lots of modules with abstracts The great new [modulename]. No
matter what wiz-bang new module starter system somebody comes up with,
there will be some kind of boilerplate text. Unless maybe it asks you
to write
* Robert Rothenberg [EMAIL PROTECTED] [2005-08-21 13:40]:
No matter what wiz-bang new module starter system somebody
comes up with, there will be some kind of boilerplate text.
Unless maybe it asks you to write the documentation before you
write the module.
Maybe the solution is to a)
# from Robert Rothenberg
# on Friday 19 August 2005 09:36 am:
I don't think patches to Module::Starter or similar packages will
help. The problem isn't with the starter utilities, it's what comes
out the other end when distributions are built. (So an eventual patch
for Module::Build, perhaps?)
Maybe Test::BrownPaperBag would be a good name, since the goal is
really to help module authors avoid making embarrassing mistakes.
Hmm, discovered just such a case in (at least) one of my modules that
might be picked up by a suitable test module. Looks like CPAN is
finding classes inside my
In article [EMAIL PROTECTED], Robert Rothenberg
[EMAIL PROTECTED] wrote:
I'm rather annoyed by the spate of CPAN uploads which have defaults from
h2xs or Module::Install that are not edited, things like Perl extension
for blah blah blah or A. U. Thor. In other words, stupid mistakes.
So
* _brian_d_foy [EMAIL PROTECTED] [2005-08-20 23:15]:
When you want to add something (like a standard test file), you
just add it to the sample dist. When you want to change some
boilerplate, you just change it in the sample dist. When you
want to move files around, well, you get the idea.
I'm rather annoyed by the spate of CPAN uploads which have defaults from
h2xs or Module::Install that are not edited, things like Perl extension
for blah blah blah or A. U. Thor. In other words, stupid mistakes.
So I've been toying ideas for a module which checks for files which
match
On 8/18/05, Robert Rothenberg [EMAIL PROTECTED] wrote:
So I've been toying ideas for a module which checks for files which
match regexps of known defaults. Maybe also check that the ChangeLog
has a version which matches the VERSION in the POD (since authors often
forget to update it).
Heh -- amusing. But then, if the authors don't change defaults, why would
they bother to run these tests? And I doubt they would ever be automatic
in something like Module::Build -- that's not the philosophy, nor do I think
it would ever be a prereq for Module::Build. (It could be an addon
On Fri, Aug 19, 2005 at 03:21:00AM -0700, David Baird ([EMAIL PROTECTED]) wrote:
Maybe you could combine these techniques
to keep it really simple for the really stupid.
How about if we get off our thrones and stop referring to people who
take the time to put out their code on CPAN as really
On 8/19/05, Andy Lester [EMAIL PROTECTED] wrote:
On Fri, Aug 19, 2005 at 03:21:00AM -0700, David Baird ([EMAIL PROTECTED])
wrote:
Maybe you could combine these techniques
to keep it really simple for the really stupid.
How about if we get off our thrones and stop referring to people who
On Fri, Aug 19, 2005 at 07:40:10AM -0700, David Baird ([EMAIL PROTECTED]) wrote:
Sure, but the point remains, perhaps better stated as make it really
easy for the really lazy, including me. I'm all in favour of modules
that help *me* not make an ass of myself. We're all potential victims
of
David Baird wrote:
Sure, but the point remains, perhaps better stated as make it really
easy for the really lazy, including me. I'm all in favour of modules
that help *me* not make an ass of myself. We're all potential victims
of our own stupidity.
Maybe a better approach is to improve the
I don't think patches to Module::Starter or similar packages will help.
The problem isn't with the starter utilities, it's what comes out the
other end when distributions are built. (So an eventual patch for
Module::Build, perhaps?)
Anyhow, when a prototype is ready I'll post an
David Baird [EMAIL PROTECTED] writes:
On 8/19/05, Andy Lester [EMAIL PROTECTED] wrote:
On Fri, Aug 19, 2005 at 03:21:00AM -0700, David Baird ([EMAIL PROTECTED])
wrote:
Maybe you could combine these techniques
to keep it really simple for the really stupid.
How about if we get off our
29 matches
Mail list logo
