Thanx, I'll try to comply.
Do you know of a good CPAN contributor FAQ? I have a couple of
questions.
1. Some of the modules I published yesterday include testcases that are
also *.pm's but for which there is absolutely no point in indexing
them. They often have the same names in different modules, including same
namespace (testcases::) They are not installed during the installation.
Is there a way to mark them as "internal" or "uninstallable", so that
CPAN can ignore them?
Probably making that a part of META.yml would be nice if there is no way
currently..
2. For the DB::Appgen -- what would you suggest? To compile and test
properly it has to know the location of libraries I can't redistribute
-- they are commercial and DB::Appgen is simply an interface sugar
module for Perl.
Would something like just 'die "Need libraries location"' suffice? It'll
still fail automatic testing, but at least it won't hog resources..
Andrew.
On Fri, Jan 14, 2005 at 11:46:52AM -0500, Max Maischein via RT wrote:
Show quoted text>
> This message about DB-Appgen was sent to you by corion@corion.net <corion@corion.net> via rt.cpan.org
>
> Full context and any attached attachments can be found at:
> <URL:
https://rt.cpan.org/Ticket/Display.html?id=9726 >
>
> Hello,
>
> please use the C<prompt> function of ExtUtils::MakeMaker instead of
> reading from STDIN, as that function can supply a default.
>
> Also please do not enter an infinite loop, if no suitable input is read.
> If your module is installed unattended/automatically, there is nobody to
> give it an answer. Also, this prevents automatic testing of your module.
>
> Thanks,
> -max
