Re: Public Tags of Releases

  101201
November 29, 2017 11:09 phpdev@ehrhardt.nl (Jan Ehrhardt)
Anatol Belski in php.internals (Tue, 28 Nov 2017 19:29:41 +0000):
>By the current terms - there's no release until the announcement. Tags >are a virtually internal thing. For a number of people the tarball is >the actual release. The Windows builds are done from the tag, that's >specific.
FWIW: I am using the zip's at github, like https://github.com/php/php-src/archive/php-7.2.0.zip -- Jan
  101203
November 29, 2017 14:37 johannes@schlueters.de (Johannes =?ISO-8859-1?Q?Schl=FCter?=)
On Mi, 2017-11-29 at 12:09 +0100, Jan Ehrhardt wrote:
> FWIW: I am using the zip's at github, like > https://github.com/php/php-src/archive/php-7.2.0.zip
Contrary to "official" release tarballs those don't contain generated parsers etc. thus behavior might be different i.e. due to different bison versions being used. (sohuldn't be, but happened in the past) Also they don't contain ready to use configure scripts (for unix-like systems) thus a (Linux/Unix/Mac) user needs right versions of auto tools. johannes
  101204
November 29, 2017 14:43 lists@rhsoft.net ("lists@rhsoft.net")
Am 29.11.2017 um 15:37 schrieb Johannes Schlüter:
> On Mi, 2017-11-29 at 12:09 +0100, Jan Ehrhardt wrote: >> FWIW: I am using the zip's at github, like >> https://github.com/php/php-src/archive/php-7.2.0.zip > > Contrary to "official" release tarballs those don't contain generated > parsers etc. thus behavior might be different i.e. due to different > bison versions being used. (sohuldn't be, but happened in the past) > Also they don't contain ready to use configure scripts (for unix-like > systems) thus a (Linux/Unix/Mac) user needs right versions of auto > tools
same applies to compilers, compiler flags and system library versions anyways # rebuild 'data_file.c' from current system libmagic starting with PHP 7.2 and when /usr/bin/php is installed %if "%{version}" >= "7.2.0" if [ -f /usr/bin/php ]; then /usr/bin/php ext/fileinfo/create_data_file.php /usr/share/misc/magic.mgc > ext/fileinfo/data_file.c fi %endif # generate zend-vm when /usr/bin/php is installed %if "%{version}" >= "7.2.0" if [ -f /usr/bin/php ]; then /usr/bin/php Zend/zend_vm_gen.php --with-vm-kind=HYBRID fi %else if [ -f /usr/bin/php ]; then /usr/bin/php Zend/zend_vm_gen.php --with-vm-kind=CALL fi %endif # force use of system libtool and regenerate configure scripts cat `aclocal --print-ac-dir`/{libtool,ltoptions,ltsugar,ltversion,lt~obsolete}.m4 >> aclocal.m4 libtoolize --force --copy --quiet cat `aclocal --print-ac-dir`/{libtool,ltoptions,ltsugar,ltversion,lt~obsolete}.m4 >build/libtool.m4 %if "%{version}" >= "7.2.0" touch configure.ac %else touch configure.in %endif ../buildconf --force
  101205
November 29, 2017 14:52 johannes@schlueters.de (Johannes =?ISO-8859-1?Q?Schl=FCter?=)
On Mi, 2017-11-29 at 15:43 +0100, lists@rhsoft.net wrote:
> Am 29.11.2017 um 15:37 schrieb Johannes Schlüter: > > > > On Mi, 2017-11-29 at 12:09 +0100, Jan Ehrhardt wrote: > > > > > > FWIW: I am using the zip's at github, like > > > https://github.com/php/php-src/archive/php-7.2.0.zip > > Contrary to "official" release tarballs those don't contain > > generated > > parsers etc. thus behavior might be different i.e. due to different > > bison versions being used. (sohuldn't be, but happened in the past) > > Also they don't contain ready to use configure scripts (for unix- > > like > > systems) thus a (Linux/Unix/Mac) user needs right versions of auto > > tools > same applies to compilers, compiler flags and system library > versions  > anyways >
This is true, but usually has less impact. bison&co historically are less stable than compiler support for language features we use. Third party libraries used in extensions are another complex story. Which is why we bundle some libs. johannes