[poe-commits] poe/lib/ExtUtils AutoInstall.pm,1.1,1.2
Brought to you by:
rcaputo
Menu
▾
▴
[poe-commits] poe/lib/ExtUtils AutoInstall.pm,1.1,1.2
|
From: <rc...@us...> - 2002-06-30 21:37:49
|
Update of /cvsroot/poe/poe/lib/ExtUtils
In directory usw-pr-cvs1:/tmp/cvs-serv7000
Modified Files:
AutoInstall.pm
Log Message:
Updated to ExtUtils::AutoInstall 0.33.
Index: AutoInstall.pm
===================================================================
RCS file: /cvsroot/poe/poe/lib/ExtUtils/AutoInstall.pm,v
retrieving revision 1.1
retrieving revision 1.2
diff -C2 -d -r1.1 -r1.2
*** AutoInstall.pm 21 May 2002 23:02:22 -0000 1.1
--- AutoInstall.pm 30 Jun 2002 21:37:46 -0000 1.2
***************
*** 1,7 ****
# $File: //member/autrijus/ExtUtils-AutoInstall/AutoInstall.pm $
! # $Revision$ $Change: 4058 $ $DateTime: 2002/04/30 16:34:09 $
package ExtUtils::AutoInstall;
! $ExtUtils::AutoInstall::VERSION = '0.32';
use strict;
--- 1,7 ----
# $File: //member/autrijus/ExtUtils-AutoInstall/AutoInstall.pm $
! # $Revision$ $Change: 1 $ $DateTime: 2002/06/11 08:35:12 $
package ExtUtils::AutoInstall;
! $ExtUtils::AutoInstall::VERSION = '0.33';
use strict;
***************
*** 16,21 ****
=head1 VERSION
! This document describes version 0.32 of B<ExtUtils::AutoInstall>,
! released May 20, 2002.
=head1 SYNOPSIS
--- 16,21 ----
=head1 VERSION
! This document describes version 0.33 of B<ExtUtils::AutoInstall>,
! released June 20, 2002.
=head1 SYNOPSIS
***************
*** 31,34 ****
--- 31,35 ----
." Fetching $p\n"and do{eval{require CPANPLUS;CPANPLUS::install
$p};eval"use $p $v;1"or eval{require CPAN;CPAN::install$p};eval
+ "use $p $v;1"or die"Please install $p $v manually first...\n"}}
use ExtUtils::AutoInstall (
***************
*** 96,100 ****
The B<Core Features> marked by the name C<-core> will double-check
with the user, if the user chooses not to install the modules that
! belongs to it. This differs with the pre-0.26 'silent install'
behaviour.
--- 97,101 ----
The B<Core Features> marked by the name C<-core> will double-check
with the user, if the user chooses not to install the modules that
! belongs to it. This differs with the pre-0.26 'silent install'
behaviour.
***************
*** 103,107 ****
The dependencies are expressed as pairs of C<Module> => C<version>
! inside an a array reference. If the order does not matter, and there
are no C<-default>, C<-tests> or C<-skiptests> directives for that
feature, you may also use a hash reference.
--- 104,108 ----
The dependencies are expressed as pairs of C<Module> => C<version>
! inside an a array reference. If the order does not matter, and there
are no C<-default>, C<-tests> or C<-skiptests> directives for that
feature, you may also use a hash reference.
***************
*** 116,125 ****
The actual installation happens at the end of the C<make config>
! target; i.e. both C<make test> and C<make install> will trigger the
installation of required modules.
If it's not running under B<CPAN>, the installer will probe for
an active connection by trying to resolve the domain C<cpan.org>,
! and check for the user's permission to use B<CPAN>. If all went
well, a separate B<CPAN> instance is created to install the required
modules.
--- 117,126 ----
The actual installation happens at the end of the C<make config>
! target; both C<make test> and C<make install> will trigger the
installation of required modules.
If it's not running under B<CPAN>, the installer will probe for
an active connection by trying to resolve the domain C<cpan.org>,
! and check for the user's permission to use B<CPAN>. If all went
well, a separate B<CPAN> instance is created to install the required
modules.
***************
*** 142,157 ****
flags if your effective uid is 0 (root), unless you explicitly disable
it by setting B<CPAN>'s C<make_install_arg> configuration option (or
! the C<makeflags> option of B<CPANPLUS>) to include C<UNINST=0>. This
I<may> cause dependency problems if you are using a fine-tuned directory
! structure for your site. Please consult L<CPAN/FAQ> for an explanation
in detail.
If B<Sort::Versions> is available, it will be used to compare the
required version with the existing module's version and the CPAN
! module's. Otherwise it silently falls back to use I<cmp>. This may
cause inconsistent behaviours in pathetic situations.
B<Inline::MakeMaker> is not happy with this module, since it prohibits
! competing C<MY::postamble> functions. Patches welcome.
=head1 NOTES
--- 143,158 ----
flags if your effective uid is 0 (root), unless you explicitly disable
it by setting B<CPAN>'s C<make_install_arg> configuration option (or
! the C<makeflags> option of B<CPANPLUS>) to include C<UNINST=0>. This
I<may> cause dependency problems if you are using a fine-tuned directory
! structure for your site. Please consult L<CPAN/FAQ> for an explanation
in detail.
If B<Sort::Versions> is available, it will be used to compare the
required version with the existing module's version and the CPAN
! module's. Otherwise it silently falls back to use I<cmp>. This may
cause inconsistent behaviours in pathetic situations.
B<Inline::MakeMaker> is not happy with this module, since it prohibits
! competing C<MY::postamble> functions. Patches welcome.
=head1 NOTES
***************
*** 159,182 ****
Since this module is needed before writing F<Makefile>, it makes
little use as a CPAN module; hence each distribution must include
! it in full. The only alternative I'm aware of, namely prompting
! in F<Makefile.PL> to force user install it (cf. the B<Template>
Toolkit's dependency on B<AppConfig>) is not very desirable either.
The current compromise is to add the bootstrap code listed in the
L</SYNOPSIS> before every script, but that ain't pretty, and won't
! work without internet connection.
Since we do not want all future options of B<ExtUtils::AutoInstall>
to be painfully detected manually like above, this module provides
! a I<bootstrapping> mechanism via the C<-version> flag. If a newer
version is needed by the F<Makefile.PL>, it will go ahead to fetch
a new version, reload it into memory, and pass the arguments forward.
! If you have any suggestions, please let me know. Thanks.
=head1 ENVIRONMENT
B<ExtUtils::AutoInstall> uses a single environment variable,
! C<PERL_EXTUTILS_AUTOINSTALL>. It's taken as the command line argument
passed to F<Makefile.PL>; you could set it to either C<--defaultdeps>
or C<--skipdeps> to avoid interactive behaviour.
--- 160,183 ----
Since this module is needed before writing F<Makefile>, it makes
little use as a CPAN module; hence each distribution must include
! it in full. The only alternative I'm aware of, namely prompting
! in F<Makefile.PL> to force user install it (cf. the B<Template>
Toolkit's dependency on B<AppConfig>) is not very desirable either.
The current compromise is to add the bootstrap code listed in the
L</SYNOPSIS> before every script, but that ain't pretty, and won't
! work without an internet connection.
Since we do not want all future options of B<ExtUtils::AutoInstall>
to be painfully detected manually like above, this module provides
! a I<bootstrapping> mechanism via the C<-version> flag. If a newer
version is needed by the F<Makefile.PL>, it will go ahead to fetch
a new version, reload it into memory, and pass the arguments forward.
! If you have any suggestions, please let me know. Thanks.
=head1 ENVIRONMENT
B<ExtUtils::AutoInstall> uses a single environment variable,
! C<PERL_EXTUTILS_AUTOINSTALL>. It's taken as the command line argument
passed to F<Makefile.PL>; you could set it to either C<--defaultdeps>
or C<--skipdeps> to avoid interactive behaviour.
***************
*** 687,691 ****
The test script included in the B<ExtUtils::AutoInstall> distribution
contains code adapted from Michael Schwern's B<Test::More> under the
! I<Artistic License>. Please refer to F<t/AutoInstall.t> for details.
Thanks also to Jesse Vincent for suggesting the semantics of various
--- 688,692 ----
The test script included in the B<ExtUtils::AutoInstall> distribution
contains code adapted from Michael Schwern's B<Test::More> under the
! I<Artistic License>. Please refer to F<t/AutoInstall.t> for details.
Thanks also to Jesse Vincent for suggesting the semantics of various
|