Re: repost: RFC: CPAN::Grab

2002-03-22 Thread Martyn J. Pearce

On Thu, Mar 21, 2002 at 01:16:10AM -0500, Ilya Zakharevich wrote:
  1) The PREREQ_PM facility informs the user of missing modules, but not
  where to find them.  Not every module (in the Perl sense) comes in a
  module (in the CPAN sense) of the same name.
 
 Why should it?  PREREQ_PM specifies
 
   Distribution depends on PM-files
 
 PAUSE indexer specifies
 
   PM-file is contained in a distribution
 
 CPAN.pm uses both pieces of info to do what it should.  What I am missing?

a) That not all modules exist on CPAN.  (some are specific to a company, some
   on sourceforge or similar).

b) That some package names may exist in multiple modules.

c) That whilst Perl supports CPAN, it's not mandatory (nor should it be).  We
   should, however, support those who won't/can't use it.

  2) There is no handling of required executables.
 
 Is not a problem as far as the executable comes with a (dummy?)
 module.

Not all modules are written in perl.  I have a module that uses the par
command, for example.

Mx.



Re: repost: RFC: CPAN::Grab

2002-03-22 Thread Ilya Zakharevich

On Fri, Mar 22, 2002 at 09:44:41AM +, Martyn J. Pearce wrote:
 On Thu, Mar 21, 2002 at 01:16:10AM -0500, Ilya Zakharevich wrote:
   1) The PREREQ_PM facility informs the user of missing modules, but not
   where to find them.  Not every module (in the Perl sense) comes in a
   module (in the CPAN sense) of the same name.
^
 See below

 a) ... not all modules exist on CPAN.  (some are specific to a company, some
on sourceforge or similar).

So you are retracting the same name part, right?

 b) That some package names may exist in multiple modules.

This is so broken that I see little sense to discuss this situation...

 c) That whilst Perl supports CPAN, it's not mandatory (nor should it be).  We
should, however, support those who won't/can't use it.

What for???  Do you also want to support people who  won't/can't use
modules with 'e' in the module name?

   2) There is no handling of required executables.
  
  Is not a problem as far as the executable comes with a (dummy?)
  module.
 
 Not all modules are written in perl.  I have a module that uses the par
 command, for example.

So code Makefile.PL to warn user if par is not available (with install
instructions if needed).  See for example Math::Pari, which will
auto-download GP/PARI if not found on the system.

Why should MakeMaker do the work which is easier to do in the module?

Ilya