[Module-build-general] ANNOUNCE: Module::Build 0.17 -> CPAN

[Ken W. <ke...@ma...>]

The uploaded file

     Module-Build-0.17.tar.gz

has entered CPAN as

   file: $CPAN/authors/id/K/KW/KWILLIAMS/Module-Build-0.17.tar.gz
   size: 58502 bytes
    md5: dcf6c4f700217388f15280e912ebf6b7

There are still a lot of things in the queue to do, but I wanted to get 
a release out since there's been a lot of progress too.

Note that I'm trying to start using http://rt.cpan.org/ for bug & 
feature tracking.

Changes since 0.16:

0.17  Sat Mar 29 18:06:01 CST 2003

  - Now works under perl 5.005_03.  [Richard Cramp]

  - When building blib/ , .PL files are now processed before doing
    anything else.  This means .PL files can be used in any of the
    other contexts.

  - The locating and processing of .pm, .pod, .xs, .PL files and script
    files are now isolated into their own methods.  This is aimed
    toward providing a stable interface for this stuff, so they can be
    overridden, parameterized, etc.  They're not quite stable yet,
    though.

  - The internal lib_to_blib() method has gone away, because processing
    is now done by smaller specialized methods.  This method had some
    duplicate assumptions about filenames that it's nice to get rid of.

  - .PL files are no longer automatically processed in the c_source
    directory, they must be specified manually in a 'PL_files'
    parameter.

  - Mention in the docs that it's useful to do "PL_FILES => {}" in a
    Makefile.PL if you're using both a Makefile.PL and a
    Build.PL. [Dom]

  - Add several options to the 'license' field, so that we're in better
    sync with PAUSE and CPAN options. [Andreas Koenig]

  - Created a find_perl_interpreter() method that tries to locate the
    currently executing perl interpreter.  Following a suggestion from
    Nicholas Clark <ni...@cc...> for Inline, we prefer an absolute
    path in $^X, then an existent path in $Config{perlpath}, then
    whatever's in $^X.

  - Use the aforementioned perl to run scripts in run_perl_script().
    This fixes the spurious warning "WARNING: Configuration was
    initially created with 'foo', but we are now using 'bar'" that
    appeared a lot in version 0.16.

  -Ken