+
+Many thanks to all the contributors and supporters!
+
+Regards,
+Fake
+
+php-1.2.3.tar.bz2
+SHA256 hash: c7337212e655325d499ea8108fa76f69ddde2fff7cb0fad36aa63eed540cb8a5
+PGP signature:
+-----BEGIN PGP SIGNATURE-----
+-----END PGP SIGNATURE-----
+
+
+php-1.2.3.tar.gz
+SHA256 hash: 8565fa8733c640b60da5ab4944bf2d4081f859915b39e29b3af26cf23443ed97
+PGP signature:
+-----BEGIN PGP SIGNATURE-----
+-----END PGP SIGNATURE-----
+
+
+php-1.2.3.tar.xz
+SHA256 hash:
+f7950ca034b15a78f5de9f1b22f4d9bad1dd497114d175cb1672a4ca78077af5
+PGP signature:
+-----BEGIN PGP SIGNATURE-----
+-----END PGP SIGNATURE-----
diff --git a/bin/sync-pregen.php b/bin/sync-pregen.php
new file mode 100644
index 0000000000..a210d62688
--- /dev/null
+++ b/bin/sync-pregen.php
@@ -0,0 +1,49 @@
+ $varPath . '/pregen-events.inc',
+ 'include/pregen-news.inc' => $varPath . '/pregen-news.inc',
+ 'include/pregen-confs.inc' => $varPath . '/pregen-confs.inc',
+];
+
+fwrite(STDOUT, "Copying data from production server into local directories:\n");
+fwrite(STDOUT, "Do not commit these files!\n");
+
+foreach ($overridePaths as $sourcePath => $saveTo) {
+ $url = 'https://www.php.net/' . $sourcePath;
+ $source = @file_get_contents($url);
+ if ($source === false) {
+ fwrite(STDERR, "Unable to read " . $url . "\n");
+ exit(1);
+ }
+
+ $success = file_put_contents($saveTo, $source);
+ if ($success === false) {
+ fwrite(STDERR, "Unable to write to " . $saveTo . "\n");
+ exit(1);
+ }
+
+ fwrite(STDOUT, "Copied " . $url . " to " . $saveTo . "\n");
+}
diff --git a/bin/util.php b/bin/util.php
new file mode 100644
index 0000000000..880ea6b332
--- /dev/null
+++ b/bin/util.php
@@ -0,0 +1,6 @@
+#!/usr/bin/env php
+
-
-
- This page is intended to help set up a development environment for PHP, if mistakes are found
- please report them.
-
-
-
- Improving PHP requires a working build environment to test changes, the following section deals with setting up a working build environment.
-
-
- Your build environment should have an appropriate toolchain that includes a working C compiler.
- For those not working in Microsoft Windows, you will need a working, compatible autotools installation, and at the very least a shared copy of zlib.
-
-
- For most *nix like operating systems, some external dependencies may be required to bring a build to completion;
- if a build fails because of missing headers or libraries, issuing a variant of the following command should resolve those dependencies, allowing the build to continue.
-
-
-
- For those working in Ubuntu Linux, you can run the following command to automate the installation of dependencies.
-
-
-
- If the compilation of an extension fails because of missing dependencies, Ubuntu Linux can attempt to automate the resolution of those dependencies by issuing:
-
-
-
- The following table shows what is required for Microsoft Windows users to build supported PHP versions:
-
-
-
- | PHP |
- Visual C++ |
- MS SDK |
- DEPS |
- PHP SDK |
-
-
- | 8.2 |
- Visual Studio 2019 |
- VS16 |
-
- x86,
- x64
- |
- tools |
-
-
- | 8.3 |
- Visual Studio 2019 |
- VS16 |
-
- x86,
- x64
- |
- tools |
-
-
- | 8.4 |
- Visual Studio 2022 |
- VS17 |
-
- x86,
- x64
- |
- tools |
-
-
- | 8.5 |
- Visual Studio 2022 |
- VS17 |
-
- x86,
- x64
- |
- tools |
-
-
-
Note: If a Windows SDK is required, it is advised to install the SDK before Visual Studio.
-
-
- Windows users should now download and unzip the PHP SDK to their workspace and execute the following commands in an appropriate Visual Studio 2019/2022 Developer Command Prompt:
-
-
- Visual Studio 2019 and 2022:
-
-
-
- Windows should now change to the directory C:\path-to-workspace\phpdev\VSXX\XARCH, and consider it the root of the workspace for the current build.
-
-
- The next step for everyone is to obtain the versioned PHP sources via git:
-
-
-
- BRANCH should be replaced with an appropriate branch name, for example, PHP-8.5.
-
-
- At this point you have a working build environment and the vanilla sources for your chosen branch of PHP, it is a good idea, before you change anything at all, to create a new branch and switch to it, in preparation for your awesome changes to come.
-
-
-
-
- All operating systems now converge on (near as makes no difference) the same solutions for the rest of the build process:
-
-
- buildconf: generates the configure script for PHPconfigure: configures the build of PHP and creates Makefilemake: builds PHPmake test: runs testsuitemake install: installs PHP
-
- For Microsoft Windows operating systems, those commands look like this:
-
-
-
- While for the rest of us, those commands look like this:
-
-
-
- The configure script can customize almost every aspect of PHP, to elicit help at the console pass --help
- as the only argument to configure
-
- When configure executes, it saves the options passed in to a re-usable config.nice which executes configure when invoked.
-
-
- Upon successful completion of a build, it is recommended to run the test suite; this will help you to identify regression problems in your work,
- running the test suite can take a while; go out for a run, or a burger.
-
-
- It is also possible to run a set (directory) of tests in the following way:
-
-
-
Advertising at PHP.net and mirror sites
-
-
- The maintainers of PHP.net are definitely not interested in graphical
- banner or text ad placement deals.
-
-
-
-Contact
-
-
- Please report problems you find on PHP.net and mirror sites on GitHub.
- This allows us to follow the progress of the
- problem until it is fixed.
-
-
- For security related issues (in PHP or our websites) please contact security@php.net, or report a vulnerability on
- GitHub.
-
-
- We have published a Vulnerability Disclosure
- Policy.
-
-
- Please note that the following are NOT security issues:
-
- - Requests for help with using PHP. Please use the
- PHP General mailing list.
- - Source code to the PHP website(s) being publicly readable.
- This is on purpose.
- All of the php.net websites are available publicly on github.
- For example, you can find this site at github.com/php/web-php.
- - Requests for bug bounty payments.
- PHP is run by volunteers with literally zero budget.
- The servers are donated hardware and bandwidth.
- Your bug reports and patches are appreciated, but we can not pay you for them.
-
-
-
- If you have problems setting up PHP or using some functionality,
- or especially a program written in PHP, please ask your question on a
- support channel, since the webmasters will
- not answer any such questions.
-
-
- If you would like to contact the webmasters for some other reason, please
- write to php-webmaster@lists.php.net.
- Note that this address is mapped to a mailing list and a newsgroup, so
- every message you send will be stored in public archives at multiple
- servers.
-
-
-
diff --git a/copyright.php b/copyright.php
deleted file mode 100644
index 57233ded2c..0000000000
--- a/copyright.php
+++ /dev/null
@@ -1,52 +0,0 @@
- "footer"]);
-?>
-
-
-Website Copyright
-
-
- The code, text, PHP logo, and graphical elements on this website
- and the mirror websites (the "Site") are Copyright © 2001-
- the PHP Group. All rights reserved.
-
-
-
- Except as otherwise indicated elsewhere on this Site, you are free
- to view, download and print the documents and information available
- on this Site subject to the following conditions:
-
-
-
- -
- You may not remove any copyright or other proprietary notices
- contained in the documents and information on this Site.
-
- -
- The rights granted to you constitute a license and not a transfer
- of title.
-
- -
- The rights specified above to view, download and print the
- documents and information available on this Site are not applicable
- to the graphical elements, design or layout of this Site. These
- elements of the Site are protected by trade dress and other laws
- and may not be copied or imitated in whole or in part.
-
-
-
-
- For more information on the PHP Group and the PHP project, please see
- the PHP homepage.
-
-
-PHP Manual
-
-
- The PHP Manual is covered by a separate license, which is available
- from within the manual itself.
-
-
-(.*)