From 71b9be80d45854ea688dd76be280957c26c207da Mon Sep 17 00:00:00 2001 From: David Golden Date: Wed, 22 Feb 2012 15:47:56 -0500 Subject: ExtUtils::CBuilder - add dual-life support files Adds Makefile.PL, LICENSE, etc. and updates Changes for work in blead from 5.14.0 --- MANIFEST | 5 + Porting/Maintainers.pl | 1 - dist/ExtUtils-CBuilder/Changes | 428 ++++++++++++++++++++++++++++++++++ dist/ExtUtils-CBuilder/LICENSE | 379 ++++++++++++++++++++++++++++++ dist/ExtUtils-CBuilder/MANIFEST.SKIP | 2 + dist/ExtUtils-CBuilder/Makefile.PL | 51 ++++ dist/ExtUtils-CBuilder/README.release | 44 ++++ 7 files changed, 909 insertions(+), 1 deletion(-) create mode 100644 dist/ExtUtils-CBuilder/Changes create mode 100644 dist/ExtUtils-CBuilder/LICENSE create mode 100644 dist/ExtUtils-CBuilder/MANIFEST.SKIP create mode 100644 dist/ExtUtils-CBuilder/Makefile.PL create mode 100644 dist/ExtUtils-CBuilder/README.release diff --git a/MANIFEST b/MANIFEST index fe244748e3..a56baa45ce 100644 --- a/MANIFEST +++ b/MANIFEST @@ -3099,6 +3099,7 @@ dist/Dumpvalue/t/Dumpvalue.t See if Dumpvalue works dist/Env/lib/Env.pm Map environment into ordinary variables dist/Env/t/array.t See if Env works for arrays dist/Env/t/env.t See if Env works +dist/ExtUtils-CBuilder/Changes EU-CB change log dist/ExtUtils-CBuilder/lib/ExtUtils/CBuilder/Base.pm Base class for ExtUtils::CBuilder methods dist/ExtUtils-CBuilder/lib/ExtUtils/CBuilder/Platform/aix.pm CBuilder methods for AIX dist/ExtUtils-CBuilder/lib/ExtUtils/CBuilder/Platform/cygwin.pm CBuilder methods for cygwin @@ -3112,6 +3113,10 @@ dist/ExtUtils-CBuilder/lib/ExtUtils/CBuilder/Platform/Windows/GCC.pm CBuilder me dist/ExtUtils-CBuilder/lib/ExtUtils/CBuilder/Platform/Windows/MSVC.pm CBuilder methods for Windows dist/ExtUtils-CBuilder/lib/ExtUtils/CBuilder/Platform/Windows.pm CBuilder methods for Windows dist/ExtUtils-CBuilder/lib/ExtUtils/CBuilder.pm Compile and link C code for Perl modules +dist/ExtUtils-CBuilder/LICENSE EU-CB license +dist/ExtUtils-CBuilder/Makefile.PL EU-CB configuration script +dist/ExtUtils-CBuilder/MANIFEST.SKIP EU-CB release support +dist/ExtUtils-CBuilder/README.release EU-CB release instructions dist/ExtUtils-CBuilder/t/00-have-compiler.t ExtUtils::CBuilder tests dist/ExtUtils-CBuilder/t/01-basic.t tests for ExtUtils::CBuilder dist/ExtUtils-CBuilder/t/02-link.t tests for ExtUtils::CBuilder diff --git a/Porting/Maintainers.pl b/Porting/Maintainers.pl index 77b3e0a8a8..e9fc764a3c 100755 --- a/Porting/Maintainers.pl +++ b/Porting/Maintainers.pl @@ -674,7 +674,6 @@ use File::Glob qw(:case); 'MAINTAINER' => 'dagolden', 'DISTRIBUTION' => 'DAGOLDEN/ExtUtils-CBuilder-0.280202.tar.gz', 'FILES' => q[dist/ExtUtils-CBuilder], - 'EXCLUDED' => [qr/^xt/], 'UPSTREAM' => 'blead', }, diff --git a/dist/ExtUtils-CBuilder/Changes b/dist/ExtUtils-CBuilder/Changes new file mode 100644 index 0000000000..3f731fb472 --- /dev/null +++ b/dist/ExtUtils-CBuilder/Changes @@ -0,0 +1,428 @@ +Revision history for Perl extension ExtUtils::CBuilder. + +0.280205 - 2011-12-20 (Perl v5.15.6) + + Fixed: + + - Fixed bug picking up ccflags from Config + +0.280204 - 2011-06-20 (Perl v5.15.0) + + Minor: + + - Quotation style cleanup + +0.280203 - 2011-05-14 (Perl v5.14.0) + + Fixed: + + - Appends CFLAGS and LDFLAGS environments instead of overriding + + - Reset ccflags on compilation for VMS. + + Changed: + + - Refactored OS name mapping to use Perl::OSType + +0.280202 - Sun Jan 23 10:47:51 EST 2011 + + - Different file names used for test files; allows EU::CB tests + to be run in parallel. [Florian Ragwitz] + +0.280201 - Fri Jan 21 15:16:36 EST 2011 + + Fixed: + + - t/04-base.t no longer attempt to compile or link as this provokes + failures on main platforms + + - Various typo fixes in Pod or comments + +0.2802 - Sun Dec 12 07:22:43 EST 2010 + + Fixed: + + - Incorporated another t/04-base.t fix from bleadperl + [Chris Williams] + +0.2801 - Wed Dec 8 21:36:56 EST 2010 + + Fixed: + + - Fixed spurious t/04-base.t failure when run from Perl core + [David Golden] + +0.2800 - Mon Dec 6 16:05:46 EST 2010 + + - No changes from 0.27_07 + +0.27_07 - Wed Sep 29 21:48:55 EDT 2010 + + Fixed: + + - Fixed t/02-link.t on perl < 5.8 + +0.27_06 - Mon Sep 27 15:29:54 EDT 2010 + + Fixed: + + - Preserves exit status on VMS [Craig Berry] + + - Fix Win32 split_like_shell escaping [Christian Walde] + +0.27_05 - Wed Jul 28 15:29:59 EDT 2010 + + Fixed: + + - Tests no longer fail if user has set the CC environment variable + +0.27_04 - Mon Jul 26 22:41:43 EDT 2010 + + Added: + - handle c compiler and c++ compiler separately + (adds requirement for IPC::Cmd) [Jens Rehsack] + + Others: + - rely on File::Temp::tempfile and File::Spec::tmpdir to + get unique file name for checking for compiler + [Jens Rehsack] + + - Code base modernization and substantial code coverage improvments + [Jim Keenan] + +0.2703 - Tue Mar 16 17:10:55 EDT 2010 + + Bugs fixed: + - fixed tests for Windows and MSVC [Jan Dubois] + +0.2702 - Mon Feb 22 15:10:52 EST 2010 + + Bugs fixed: + - compile() changes in 0.2701 did not work on Windows. Now fixed. + +0.2701 - Tue Feb 16 09:12:45 EST 2010 + + Bugs fixed: + - compile() now accepts both string & array for 'include_dirs' + argument, as documented.(RT#54606) [Alberto Simões] + +0.27 - Thu Oct 29 21:29:56 EDT 2009 + + Other: + - Removed Build.PL to avoid creating a circular dependency + - Added version numbers to Windows compiler driver modules + +0.26_05 - Sun Oct 25 17:29:02 EDT 2009 + + Bugs fixed: + - Fixed t/02link.t failures on cygwin with Perl 5.8 [David Golden] + + Other: + - Made have_compiler (and have_cplusplus) quiet without echoing + the test command to STDOUT [David Golden] + +0.26_04 - Mon Oct 19 21:57:46 EDT 2009 + + Enhancements: + - Added 'have_cplusplus()' method to check for C++ support + - Added patches for building Perl with mingw64 [Sisyphus] + - Allow CC environment variable to override $Config{cc} + + Bugs fixed: + - Fixed link executable command for Win32 MSVC (RT#40819) [Cosimo + Streppone] + - Removed MSVC version check when embedding a manifest file + (RT #43002) [Steve Hay] + + Other: + - Split Windows compiler driver packages into individual *.pm files + +0.260301 - Sat Aug 29 11:04:41 EDT 2009 + + Bugs fixed: + - Fixed linking error on Win32 with gcc compiler (RT#49000) + [kmx] + +0.2603 - Sat Jul 18 06:56:06 EDT 2009 + + Bugs fixed: + - Makefile.PL had wrong INSTALLDIRS setting for older Perls + (RT#47985) [David Golden] + +0.2602 - Sat Jul 4 10:57:12 EDT 2009 + + Bugs fixed: + - Fixed 00-have-compiler.t if $^X is a relative path [David Wheeler] + +0.2601 - Wed Jul 1 09:37:39 EDT 2009 + + Bugs fixed: + - On VMS, cleans up extra files generated during testing + [John E. Malmberg, Craig Berry] + +0.26 - Mon Jun 29 20:11:52 EDT 2009 + + - No changes from 0.25_01 + +0.25_01 - Sat Jun 27 23:13:20 EDT 2009 + + - Changed test library to Test::More + + - Added tests for have_compiler + + - Skips tests that need a compiler if have_compiler is false + + - have_compiler will try to compile in the current directory + if compiling in tmpdir fails for whatever reason + +0.25 - Fri Jun 26 16:18:13 EDT 2009 + + - Slight diagnostic improvements in link.t + +0.24_01 - Sun Mar 8 14:50:10 2009 + + - On Windows, don't generate "mt" command when CRT is statically + linked. [Jan Dubois] + + - On Cygwin, examine $Config{useshrplib} to see whether we're + supposed to be linking with a shared perl library or not. [Reini + Urban] + + - In link_executable() on Cygwin, trust $Config{ld} rather than using + $Config{cc} for linking. [Reini Urban] + + - Add 'haiku' as a Unix-like platform. [Ingo Weinhold] + +0.24 - Fri Aug 15 22:01:48 2008 + + - Added 'gnu' and 'gnukfreebsd' as Unix variants. [Niko Tyni] + + - Brought in some VMS fixes from bleadperl: "Correct and complete + CBuilder's handling of external libraries when linking on VMS." + [Craig Berry] + +0.23 - Sat Apr 19 22:28:03 2008 + + - Fixed some problems (some old, some new) with Strawberry Perl on + Windows. [Alberto Simo~es] + + - Will now install in the core perl lib directory when the user's + perl is new enough to have us in core. [Yi Ma Mao] + +0.22 - Fri Feb 8 21:52:21 2008 + + - Replaced the split_like_shell() method on Windows with a + near-no-op, which is probably more correct and has the benefit of + not messing up UNC paths. [John R. LoVerso, see + http://rt.cpan.org/Ticket/Display.html?id=26545] + + - Fixed extra_compiler_flags on Windows, they were being + ignored. [Robert May] + +0.21 - Tue Oct 30 06:46:01 2007 + + - Clean up perl_src path using Cwd::realpath(). Only affects usage + as part of the perl core. + + - Protect $., $@, $!, $^E, and $? from any clobbering that might + occur in our DESTROY method. [Zefram] + + - From bleadperl, a patch to clean up debug symbol files (.pdb for + VC++, .tds for BCC) when running have_compiler(). [Steve Hay & + Steve Peters] + +0.19 - Sun May 13 14:29:18 2007 + + - When building as part of the perl core (so this is irrelevant for + people downloading from CPAN) we now try a little harder to find + the perl sources. [Jos Boumans] + + - Fixed a part of the manifest thingy that got broken on 64-bit + Windows platforms in version 0.18. [Steve Hay, Jan Dubois] + +0.18 - Mon Mar 26 21:29:09 2007 + + - Various OS/2 fixes: + + Put .LIB file near .DEF file + + Got library-file building working better + + Handled libperl_overrides better + [Ilya Zakharevich] + + - On Windows: embed manifest files in DLLs built with Module-Build + when using VC8. [Steve Hay] + + - Added a workaround for a config error on dec_osf: the linker is + $Config{cc}, not $Config{ld}. [Jarkko Hietaniemi] + + - Borland's compiler "response files" will not pass through macro + definitions that contain quotes. The quotes get stripped and there + seems to be no way to escape them. So we leave macros on the + command line. [Randy W. Sims] + +0.18 Sat Mar 25 13:35:47 CST 2006 + + - Yet more fixes for arg_defines() on VMS. [Craig A. Berry and John + E. Malmberg] + +0.17 Wed Mar 15 22:46:15 CST 2006 + + - When we're being run from an uninstalled perl distribution + (e.g. one that's in the process of being built and tested), we + search for perl first in the current working directory. [Randy + Sims] + + - More fixing of the arg_defines() method on VMS. [Craig A. Berry and + John E. Malmberg] + +0.16 Mon Mar 13 17:08:21 CST 2006 + + - Fix quoting of command line arguments on Windows. [Yitzchak + Scott-Thoennes] + + - Provided a custom arg_defines() on VMS that does essentially the + same thing for /define that version 0.14 did for /include. [Craig + A. Berry] + + - Documented the existing 'quiet' parameter, which silences the + printing of system() commands. [Suggested by Yitzchak + Scott-Thoennes] + +0.15 Mon Oct 3 17:10:32 CDT 2005 + + - Several OS/2 fixes have been made, including: 1) adding the + necessary version string to DLLs, 2) passing the executable's name + to 'ldopts' without the .exe extension, 3) avoiding calling 'env' + via the 'shrpenv' thingy, since it triggers a fork() bug. [Ilya + Zakharevich] + + - Integrate a couple cleanup-related changes from bleadperl that + somehow never got into this copy. [Steve Hay] + + - Added a new 'defines' parameter to compile(), which gives a + platform-independant way to specify various -Dfoo=bar (or the + equivalent) compiler defines. [Randy W. Sims] + +0.14 Mon Sep 19 13:40:37 CDT 2005 + + - Several fixes have been made for VMS, including: 1) there can only + be one /include qualifier, so merge multiple /includes into one; 2) + make sure the executable is named the same way that dynaloader will + look for it; 3) make sure the option files for the exported symbols + and the PERLSHR image are passed properly to the linker. [John + E. Malmberg] + +0.13 Wed Aug 24 20:05:59 CDT 2005 + + - Several temporary files weren't being cleaned up during testing, + because the 'cleanup' mechanism was never properly implemented. + This is now fixed. [Steve Hay] + +0.12 Mon May 30 16:40:10 CDT 2005 + + - In order to integrate into the perl core, patches were contributed + that a) put a $VERSION variable in each .pm file, b) add a 'quiet' + parameter to new() to shut up some of the command-echoing, c) + checks for the perl source headers in the CORE/ directory in the + perl source tree, not in the post-installation location, and d) + adjusts the CWD when running the regression tests under the perl + core. [Yitzchak Scott-Thoennes] + + - Various parts of the code were looking for the CORE/ directory in + $Config{archlib}, $Config{installarchlib}, and $Config{archlibexp}. + Only the latter is correct, so we use that everywhere now. + [Curt Tilmes] + + - For Unix-ish platforms, link_executable() will now prefer + $Config{cc} to $Config{ld}, because that typically works + better. [Jarkko Hietaniemi and H.Merijn Brand] + + - Prelinking (invoking ExtUtils::Mksymlists to create options-files) + is now only done when we're building dynamic libraries. [Yitzchak + Scott-Thoennes] + +0.11 Tue Apr 5 20:58:41 CDT 2005 + + - Added a licensing statement to CBuilder.pm. [Spotted by Chip + Salzenberg] + +0.10 Mon Mar 14 20:18:19 CST 2005 + + - Split out a few simple routines that format how compile switches + are formatted, so that we can override them for platforms like VMS + where they're very different. + + - Fix compile() and link() on VMS. [Help from Michael Schwern and + Peter Prymmer] + +0.09 Tue Feb 8 17:57:41 CST 2005 + + - Fixed a broken link_executable() method on cygwin - it now uses + 'gcc' instead of $Config{ld} for the linking, because the latter is + actually a shell script which calls a perl script which calls gcc + in a way that only works for creating shared libraries, not + executables. + +0.08 Tue Jan 18 21:54:11 CST 2005 + + - Fixed a testing error in which I had the prototype wrong for the + main() function. [Jose Pedro Oliveira] + +0.07 Wed Jan 12 21:50:34 CST 2005 + + - Added the link_executable() method, which provides the ability to + create standalone executables. This is NOT yet implemented on + Windows, and therefore the tests for it are skipped on Win32. + [Alberto Manuel Brandao Simoes] + + - Integrated the latest split_like_shell() for Windows from + Module::Build (really need to find a better home for this code...), + which now does a much better job of handling quotes and backslashes + and so on. [Randy Sims] + + - Fixed a couple of Windows problems related to the output-file name + in link(), and some clobbering of the 'include_dirs' parameter to + compile(). [Randy Sims] + +0.06 Mon Dec 27 22:51:36 CST 2004 + + - Fixed a bug on Unix environments in which our work-around for + shell-commands like "FOO=BAR cc" (which is supposed to be turned + into "env FOO=BAR cc" to actually work) wasn't being called. + +0.05 Wed Oct 13 23:09:09 CDT 2004 + + - Fixed a bug in split_like_shell() in which leading whitespace was + creating an empty word, manifesting as something like "gcc - no + such file or directory" during tests. [Spotted by Warren L. Dodge] + + - Incorporate another split_like_shell() fix from Module::Build. + +0.04 Sun Oct 10 00:31:08 CDT 2004 + + - Changed the split_like_shell() method to use the shellwords() + function from Text::ParseWords (a core module since 5.0), which + does a much better job than the split() we were using. + + +0.03 Fri May 14 23:12:23 CDT 2004 + + - Fixed minor problems with the Build.PL file, the module names + should be quoted. + + - The VMS module declared itself with the wrong package name. + + +0.02 Fri Feb 20 10:17:40 CST 2004 + + - Fixed a bug in .../Platform/Windows.pm, in which compile() was + ignoring an 'include_dirs' argument. [Randy Sims] + + - Fixed a bug in .../Platform/Windows.pm, in which output files were + being created in the root directory \ when they should be created + in the current directory. [Randy Sims] + + +0.01 Mon Jan 12 08:12:35 CST 2004 + + - Original release, taken from Module::Build's C-building code, with + patching help from Randy Sims. diff --git a/dist/ExtUtils-CBuilder/LICENSE b/dist/ExtUtils-CBuilder/LICENSE new file mode 100644 index 0000000000..05d79c9330 --- /dev/null +++ b/dist/ExtUtils-CBuilder/LICENSE @@ -0,0 +1,379 @@ +This software is copyright (c) 2012 by Ken Williams. + +This is free software; you can redistribute it and/or modify it under +the same terms as the Perl 5 programming language system itself. + +Terms of the Perl programming language system itself + +a) the GNU General Public License as published by the Free + Software Foundation; either version 1, or (at your option) any + later version, or +b) the "Artistic License" + +--- The GNU General Public License, Version 1, February 1989 --- + +This software is Copyright (c) 2012 by Ken Williams. + +This is free software, licensed under: + + The GNU General Public License, Version 1, February 1989 + + GNU GENERAL PUBLIC LICENSE + Version 1, February 1989 + + Copyright (C) 1989 Free Software Foundation, Inc. + 51 Franklin St, Suite 500, Boston, MA 02110-1335 USA + + Everyone is permitted to copy and distribute verbatim copies + of this license document, but changing it is not allowed. + + Preamble + + The license agreements of most software companies try to keep users +at the mercy of those companies. By contrast, our General Public +License is intended to guarantee your freedom to share and change free +software--to make sure the software is free for all its users. The +General Public License applies to the Free Software Foundation's +software and to any other program whose authors commit to using it. +You can use it for your programs, too. + + When we speak of free software, we are referring to freedom, not +price. Specifically, the General Public License is designed to make +sure that you have the freedom to give away or sell copies of free +software, that you receive source code or can get it if you want it, +that you can change the software or use pieces of it in new free +programs; and that you know you can do these things. + + To protect your rights, we need to make restrictions that forbid +anyone to deny you these rights or to ask you to surrender the rights. +These restrictions translate to certain responsibilities for you if you +distribute copies of the software, or if you modify it. + + For example, if you distribute copies of a such a program, whether +gratis or for a fee, you must give the recipients all the rights that +you have. You must make sure that they, too, receive or can get the +source code. And you must tell them their rights. + + We protect your rights with two steps: (1) copyright the software, and +(2) offer you this license which gives you legal permission to copy, +distribute and/or modify the software. + + Also, for each author's protection and ours, we want to make certain +that everyone understands that there is no warranty for this free +software. If the software is modified by someone else and passed on, we +want its recipients to know that what they have is not the original, so +that any problems introduced by others will not reflect on the original +authors' reputations. + + The precise terms and conditions for copying, distribution and +modification follow. + + GNU GENERAL PUBLIC LICENSE + TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION + + 0. This License Agreement applies to any program or other work which +contains a notice placed by the copyright holder saying it may be +distributed under the terms of this General Public License. The +"Program", below, refers to any such program or work, and a "work based +on the Program" means either the Program or any work containing the +Program or a portion of it, either verbatim or with modifications. Each +licensee is addressed as "you". + + 1. You may copy and distribute verbatim copies of the Program's source +code as you receive it, in any medium, provided that you conspicuously and +appropriately publish on each copy an appropriate copyright notice and +disclaimer of warranty; keep intact all the notices that refer to this +General Public License and to the absence of any warranty; and give any +other recipients of the Program a copy of this General Public License +along with the Program. You may charge a fee for the physical act of +transferring a copy. + + 2. You may modify your copy or copies of the Program or any portion of +it, and copy and distribute such modifications under the terms of Paragraph +1 above, provided that you also do the following: + + a) cause the modified files to carry prominent notices stating that + you changed the files and the date of any change; and + + b) cause the whole of any work that you distribute or publish, that + in whole or in part contains the Program or any part thereof, either + with or without modifications, to be licensed at no charge to all + third parties under the terms of this General Public License (except + that you may choose to grant warranty protection to some or all + third parties, at your option). + + c) If the modified program normally reads commands interactively when + run, you must cause it, when started running for such interactive use + in the simplest and most usual way, to print or display an + announcement including an appropriate copyright notice and a notice + that there is no warranty (or else, saying that you provide a + warranty) and that users may redistribute the program under these + conditions, and telling the user how to view a copy of this General + Public License. + + d) You may charge a fee for the physical act of transferring a + copy, and you may at your option offer warranty protection in + exchange for a fee. + +Mere aggregation of another independent work with the Program (or its +derivative) on a volume of a storage or distribution medium does not bring +the other work under the scope of these terms. + + 3. You may copy and distribute the Program (or a portion or derivative of +it, under Paragraph 2) in object code or executable form under the terms of +Paragraphs 1 and 2 above provided that you also do one of the following: + + a) accompany it with the complete corresponding machine-readable + source code, which must be distributed under the terms of + Paragraphs 1 and 2 above; or, + + b) accompany it with a written offer, valid for at least three + years, to give any third party free (except for a nominal charge + for the cost of distribution) a complete machine-readable copy of the + corresponding source code, to be distributed under the terms of + Paragraphs 1 and 2 above; or, + + c) accompany it with the information you received as to where the + corresponding source code may be obtained. (This alternative is + allowed only for noncommercial distribution and only if you + received the program in object code or executable form alone.) + +Source code for a work means the preferred form of the work for making +modifications to it. For an executable file, complete source code means +all the source code for all modules it contains; but, as a special +exception, it need not include source code for modules which are standard +libraries that accompany the operating system on which the executable +file runs, or for standard header files or definitions files that +accompany that operating system. + + 4. You may not copy, modify, sublicense, distribute or transfer the +Program except as expressly provided under this General Public License. +Any attempt otherwise to copy, modify, sublicense, distribute or transfer +the Program is void, and will automatically terminate your rights to use +the Program under this License. However, parties who have received +copies, or rights to use copies, from you under this General Public +License will not have their licenses terminated so long as such parties +remain in full compliance. + + 5. By copying, distributing or modifying the Program (or any work based +on the Program) you indicate your acceptance of this license to do so, +and all its terms and conditions. + + 6. Each time you redistribute the Program (or any work based on the +Program), the recipient automatically receives a license from the original +licensor to copy, distribute or modify the Program subject to these +terms and conditions. You may not impose any further restrictions on the +recipients' exercise of the rights granted herein. + + 7. The Free Software Foundation may publish revised and/or new versions +of the General Public License from time to time. Such new versions will +be similar in spirit to the present version, but may differ in detail to +address new problems or concerns. + +Each version is given a distinguishing version number. If the Program +specifies a version number of the license which applies to it and "any +later version", you have the option of following the terms and conditions +either of that version or of any later version published by the Free +Software Foundation. If the Program does not specify a version number of +the license, you may choose any version ever published by the Free Software +Foundation. + + 8. If you wish to incorporate parts of the Program into other free +programs whose distribution conditions are different, write to the author +to ask for permission. For software which is copyrighted by the Free +Software Foundation, write to the Free Software Foundation; we sometimes +make exceptions for this. Our decision will be guided by the two goals +of preserving the free status of all derivatives of our free software and +of promoting the sharing and reuse of software generally. + + NO WARRANTY + + 9. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY +FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN +OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES +PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED +OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF +MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS +TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE +PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, +REPAIR OR CORRECTION. + + 10. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING +WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR +REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, +INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING +OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED +TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY +YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER +PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE +POSSIBILITY OF SUCH DAMAGES. + + END OF TERMS AND CONDITIONS + + Appendix: How to Apply These Terms to Your New Programs + + If you develop a new program, and you want it to be of the greatest +possible use to humanity, the best way to achieve this is to make it +free software which everyone can redistribute and change under these +terms. + + To do so, attach the following notices to the program. It is safest to +attach them to the start of each source file to most effectively convey +the exclusion of warranty; and each file should have at least the +"copyright" line and a pointer to where the full notice is found. + + + Copyright (C) 19yy + + This program is free software; you can redistribute it and/or modify + it under the terms of the GNU General Public License as published by + the Free Software Foundation; either version 1, or (at your option) + any later version. + + This program is distributed in the hope that it will be useful, + but WITHOUT ANY WARRANTY; without even the implied warranty of + MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the + GNU General Public License for more details. + + You should have received a copy of the GNU General Public License + along with this program; if not, write to the Free Software + Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston MA 02110-1301 USA + + +Also add information on how to contact you by electronic and paper mail. + +If the program is interactive, make it output a short notice like this +when it starts in an interactive mode: + + Gnomovision version 69, Copyright (C) 19xx name of author + Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'. + This is free software, and you are welcome to redistribute it + under certain conditions; type `show c' for details. + +The hypothetical commands `show w' and `show c' should show the +appropriate parts of the General Public License. Of course, the +commands you use may be called something other than `show w' and `show +c'; they could even be mouse-clicks or menu items--whatever suits your +program. + +You should also get your employer (if you work as a programmer) or your +school, if any, to sign a "copyright disclaimer" for the program, if +necessary. Here a sample; alter the names: + + Yoyodyne, Inc., hereby disclaims all copyright interest in the + program `Gnomovision' (a program to direct compilers to make passes + at assemblers) written by James Hacker. + + , 1 April 1989 + Ty Coon, President of Vice + +That's all there is to it! + + +--- The Artistic License 1.0 --- + +This software is Copyright (c) 2012 by Ken Williams. + +This is free software, licensed under: + + The Artistic License 1.0 + +The Artistic License + +Preamble + +The intent of this document is to state the conditions under which a Package +may be copied, such that the Copyright Holder maintains some semblance of +artistic control over the development of the package, while giving the users of +the package the right to use and distribute the Package in a more-or-less +customary fashion, plus the right to make reasonable modifications. + +Definitions: + + - "Package" refers to the collection of files distributed by the Copyright + Holder, and derivatives of that collection of files created through + textual modification. + - "Standard Version" refers to such a Package if it has not been modified, + or has been modified in accordance with the wishes of the Copyright + Holder. + - "Copyright Holder" is whoever is named in the copyright or copyrights for + the package. + - "You" is you, if you're thinking about copying or distributing this Package. + - "Reasonable copying fee" is whatever you can justify on the basis of media + cost, duplication charges, time of people involved, and so on. (You will + not be required to justify it to the Copyright Holder, but only to the + computing community at large as a market that must bear the fee.) + - "Freely Available" means that no fee is charged for the item itself, though + there may be fees involved in handling the item. It also means that + recipients of the item may redistribute it under the same conditions they + received it. + +1. You may make and give away verbatim copies of the source form of the +Standard Version of this Package without restriction, provided that you +duplicate all of the original copyright notices and associated disclaimers. + +2. You may apply bug fixes, portability fixes and other modifications derived +from the Public Domain or from the Copyright Holder. A Package modified in such +a way shall still be considered the Standard Version. + +3. You may otherwise modify your copy of this Package in any way, provided that +you insert a prominent notice in each changed file stating how and when you +changed that file, and provided that you do at least ONE of the following: + + a) place your modifications in the Public Domain or otherwise make them + Freely Available, such as by posting said modifications to Usenet or an + equivalent medium, or placing the modifications on a major archive site + such as ftp.uu.net, or by allowing the Copyright Holder to include your + modifications in the Standard Version of the Package. + + b) use the modified Package only within your corporation or organization. + + c) rename any non-standard executables so the names do not conflict with + standard executables, which must also be provided, and provide a separate + manual page for each non-standard executable that clearly documents how it + differs from the Standard Version. + + d) make other distribution arrangements with the Copyright Holder. + +4. You may distribute the programs of this Package in object code or executable +form, provided that you do at least ONE of the following: + + a) distribute a Standard Version of the executables and library files, + together with instructions (in the manual page or equivalent) on where to + get the Standard Version. + + b) accompany the distribution with the machine-readable source of the Package + with your modifications. + + c) accompany any non-standard executables with their corresponding Standard + Version executables, giving the non-standard executables non-standard + names, and clearly documenting the differences in manual pages (or + equivalent), together with instructions on where to get the Standard + Version. + + d) make other distribution arrangements with the Copyright Holder. + +5. You may charge a reasonable copying fee for any distribution of this +Package. You may charge any fee you choose for support of this Package. You +may not charge a fee for this Package itself. However, you may distribute this +Package in aggregate with other (possibly commercial) programs as part of a +larger (possibly commercial) software distribution provided that you do not +advertise this Package as a product of your own. + +6. The scripts and library files supplied as input to or produced as output +from the programs of this Package do not automatically fall under the copyright +of this Package, but belong to whomever generated them, and may be sold +commercially, and may be aggregated with this Package. + +7. C or perl subroutines supplied by you and linked into this Package shall not +be considered part of this Package. + +8. The name of the Copyright Holder may not be used to endorse or promote +products derived from this software without specific prior written permission. + +9. THIS PACKAGE IS PROVIDED "AS IS" AND WITHOUT ANY EXPRESS OR IMPLIED +WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF +MERCHANTIBILITY AND FITNESS FOR A PARTICULAR PURPOSE. + +The End + diff --git a/dist/ExtUtils-CBuilder/MANIFEST.SKIP b/dist/ExtUtils-CBuilder/MANIFEST.SKIP new file mode 100644 index 0000000000..d1df10a92d --- /dev/null +++ b/dist/ExtUtils-CBuilder/MANIFEST.SKIP @@ -0,0 +1,2 @@ +#!include_default +README.release diff --git a/dist/ExtUtils-CBuilder/Makefile.PL b/dist/ExtUtils-CBuilder/Makefile.PL new file mode 100644 index 0000000000..e6b1d16c3a --- /dev/null +++ b/dist/ExtUtils-CBuilder/Makefile.PL @@ -0,0 +1,51 @@ +use strict; +use warnings; + +use ExtUtils::MakeMaker 6.30; + +my %WriteMakefileArgs = ( + "NAME" => "ExtUtils::CBuilder", + "VERSION_FROM" => "lib/ExtUtils/CBuilder.pm", + "ABSTRACT_FROM" => "lib/ExtUtils/CBuilder.pm", + "AUTHOR" => "Ken Williams , The Perl 5 Porters", + "BUILD_REQUIRES" => { + "Test::More" => "0.47" + }, + "CONFIGURE_REQUIRES" => { + "ExtUtils::MakeMaker" => "6.30" + }, + "EXE_FILES" => [], + "LICENSE" => "perl", + "PREREQ_PM" => { + "Cwd" => 0, + "File::Basename" => 0, + "File::Spec" => "3.13", + "File::Temp" => 0, + "IO::File" => 0, + "IPC::Cmd" => 0, + "Perl::OSType" => 0, + "Text::ParseWords" => 0 + }, +); + +unless ( eval { ExtUtils::MakeMaker->VERSION(6.56) } ) { + my $br = delete $WriteMakefileArgs{BUILD_REQUIRES}; + my $pp = $WriteMakefileArgs{PREREQ_PM}; + for my $mod ( keys %$br ) { + if ( exists $pp->{$mod} ) { + $pp->{$mod} = $br->{$mod} if $br->{$mod} > $pp->{$mod}; + } + else { + $pp->{$mod} = $br->{$mod}; + } + } +} + +delete $WriteMakefileArgs{CONFIGURE_REQUIRES} + unless eval { ExtUtils::MakeMaker->VERSION(6.52) }; + +$WriteMakefileArgs{INSTALLDIRS} = 'perl' + if $] >= 5.009005 && $] <= 5.011000; + +WriteMakefile(%WriteMakefileArgs); + diff --git a/dist/ExtUtils-CBuilder/README.release b/dist/ExtUtils-CBuilder/README.release new file mode 100644 index 0000000000..010fb258f0 --- /dev/null +++ b/dist/ExtUtils-CBuilder/README.release @@ -0,0 +1,44 @@ +Release instructions for dual-life ExtUtils::CBuilder + +1. Check out a tag/commit corresponding to the release point. This +should generally be a Perl release (dev or stable). Make sure +your working tree is clear of extraneous files. E.g. + + $ git checkout v5.15.8 + $ git clean -dxf + +2. Rsync the ExtUtils-CBuilder directory to a temporary directory for +release. E.g. + + $ rsync -av --delete dist/ExtUtils-CBuilder /tmp + +3. Change to the temp directory + + $ cd /tmp/ExtUtils-CBuilder + +4. Look at the Changes file. If it was not kept up to date in blead, +take a minute to feel sad, then update it. Remember to copy the +changes back to blead later. + +5. Configure and then make a MANIFEST + + $ perl Makefile.PL + $ make manifest + +6. Build a release directory and examine its contents, paying particular +attention to the MANIFEST and the META files + + $ make distdir + +7. Test the release directory + + $ make disttest + +8. If all looks good, create a tarball and upload it to CPAN (maybe +install CPAN::Uploader or an equivalent tool) + + $ make dist + $ cpan_upload ExtUtils-CBuilder-X.YYYZZZ.tar.gz + +9. If you updated Changes, copy that back to blead now and commit it +(or submit it as a patch if you don't have a commit bit) -- cgit v1.2.1