| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Package-Manager: Portage-2.3.3, Repoman-2.3.1
|
|
|
|
|
|
| |
Package-Manager: portage-2.3.0
RepoMan-Options: --include-arches="x86"
Signed-off-by: Agostino Sarubbo <ago@gentoo.org>
|
|
|
|
|
| |
Package-Manager: Portage-2.3.3, Repoman-2.3.1
RepoMan-Options: --ignore-arches
|
|
|
|
| |
Package-Manager: portage-2.3.3
|
|
|
|
|
|
| |
Package-Manager: portage-2.3.0
RepoMan-Options: --include-arches="amd64"
Signed-off-by: Agostino Sarubbo <ago@gentoo.org>
|
|
|
|
| |
Gentoo-Bug: 606626
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In addition to the version bumps, the (unused, hopefully) libtool
eclass was dropped from the php-5.6.30 and php-7.0.15 ebuilds
Upstream merged a fix for heimdal detection, allowing us to drop that
workaround from src_prepare. After the heimdal workaround was removed,
it then made sense to drop the autotools eclass entirely. That means
no more custom branding in the 7.0 series, but we are essentially a
vanilla upstream PHP at this point.
Gentoo-Bug: 597448
Gentoo-Bug: 597450
Package-Manager: portage-2.3.0
|
|
|
|
|
|
| |
Gentoo-Bug: 604776
Package-Manager: portage-2.3.0
|
|
|
|
|
|
| |
Package-Manager: portage-2.3.0
RepoMan-Options: --include-arches="ppc64"
Signed-off-by: Agostino Sarubbo <ago@gentoo.org>
|
|
|
|
|
|
| |
Package-Manager: portage-2.3.0
RepoMan-Options: --include-arches="ia64"
Signed-off-by: Agostino Sarubbo <ago@gentoo.org>
|
|
|
|
|
| |
Package-Manager: Portage-2.3.3, Repoman-2.3.1
RepoMan-Options: --ignore-arches
|
|
|
|
|
|
| |
Package-Manager: portage-2.3.0
RepoMan-Options: --include-arches="ppc"
Signed-off-by: Agostino Sarubbo <ago@gentoo.org>
|
|
|
|
|
| |
Package-Manager: Portage-2.3.3, Repoman-2.3.1
RepoMan-Options: --include-arches="arm"
|
|
|
|
|
|
| |
Package-Manager: portage-2.3.0
RepoMan-Options: --include-arches="sparc"
Signed-off-by: Agostino Sarubbo <ago@gentoo.org>
|
|
|
|
|
|
| |
Package-Manager: portage-2.3.0
RepoMan-Options: --include-arches="x86"
Signed-off-by: Agostino Sarubbo <ago@gentoo.org>
|
|
|
|
| |
Gentoo-Bug: 604776
|
| |
|
|
|
|
|
|
|
|
| |
This includes a change to the stable php-5.6.28, but since the
"frontbase" USE flag did not affect the package in any way, it
(famous last words) should be safe to make.
Package-Manager: portage-2.3.0
|
|
|
|
| |
Package-Manager: Portage-2.3.3, Repoman-2.3.1
|
|
|
|
|
|
| |
Gentoo-Bug: 602738
Package-Manager: portage-2.3.0
|
|
|
|
| |
Package-Manager: portage-2.3.0
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We add three new revisions, one for each supported branch of PHP. The
new revisions have a "coverage" flag, which was chosen because a few
other packages in ::gentoo have decided on the same flag name. When
enabled, USE=coverage will pull in dev-util/lcov from the Linux Test
Project, and PHP will be built with --enable-gcov.
Since users won't be running code coverage reports on the PHP source
tree itself (at least not the one used by their package manager), this
is probably only useful for extension developers who would like to run
code coverage reports on the test suites for their extensions. It also
requires GCC to work, since lcov wraps GCC's gcov. Both of those
caveats have been mentioned in the USE flag description.
Gentoo-Bug: 542178
Package-Manager: portage-2.3.0
|
|
|
|
| |
Package-Manager: portage-2.3.0
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
To help phase out the abandoned and buggy app-text/htmltidy, I tried
to make the new php:7.1 depend on app-text/tidy-html5
instead. However, since older versions of PHP do not support
tidy-html5, that causes a problem: php:7.1 cannot be installed
alongside the older versions when USE=tidy is set for both of them.
This solution is somewhat of a cop out, allowing htmltidy to be used
in php:7.1 as a last resort. The alternative would have been to
backport the tidy-html5 support to (both) older versions of PHP. That
may eventually become necessary if it looks like htmltidy will be
masked for removal; however, for now, this is the path of least
resistance.
Gentoo-Bug: 601614
Package-Manager: portage-2.3.0
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The php-fpm backend can be used to host multiple applications with
different settings and permissions. Traditionally, permissions on its
UNIX socket are granted to the "listen.owner" and "listen.group"
defined in php-fpm.conf. However, php-fpm can be compiled with POSIX
ACL support, after which the more-powerful "listen.acl_users" and
"listen.acl_groups" can be used.
This commit adds three new revisions -- one for each supported branch
of PHP. To each new revision, the "acl" USE flag has been added. When
USE=acl is set, sys-apps/acl gets pulled in as a dependency, and
"--with-fpm-acl" is passed to the configure script.
Gentoo-Bug: 601634
Package-Manager: portage-2.3.0
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is a new upstream release and the ebuild incorporates a few fixes
facilitated by upstream changes:
1. We use app-text/tidy-html5 instead of the abandoned app-text/htmltidy.
2. Upstream now detects heimdal correctly so our workaround has been
removed.
3. The custom Gentoo branding that required us to rebuild all of the
autotools files has been removed. A few build dependencies were
eliminated as a result, and the autotools and libtool eclasses were
dropped.
The changes above have associated Gentoo bugs. In addition, the hack
for bug 343481 was removed, since it had no effect on the configure
script for v7.1.0. I do not know if the fix is simply no longer
needed, or if it should be forward-ported.
Gentoo-Bug: 585474
Gentoo-Bug: 597448
Gentoo-Bug: 597450
Package-Manager: portage-2.3.0
|
|
|
|
| |
Package-Manager: portage-2.3.2
|
|
|
|
|
|
| |
Package-Manager: portage-2.3.0
RepoMan-Options: --include-arches="ia64"
Signed-off-by: Agostino Sarubbo <ago@gentoo.org>
|
|
|
|
|
|
| |
Package-Manager: portage-2.3.0
RepoMan-Options: --include-arches="sparc"
Signed-off-by: Agostino Sarubbo <ago@gentoo.org>
|
|
|
|
|
|
| |
Package-Manager: portage-2.3.0
RepoMan-Options: --include-arches="ppc"
Signed-off-by: Agostino Sarubbo <ago@gentoo.org>
|
|
|
|
|
|
| |
Package-Manager: portage-2.3.0
RepoMan-Options: --include-arches="arm"
Signed-off-by: Agostino Sarubbo <ago@gentoo.org>
|
|
|
|
|
| |
Package-Manager: portage-2.3.2
RepoMan-Options: --ignore-arches
|
|
|
|
| |
Gentoo-Bug: 599326
|
|
|
|
| |
Gentoo-Bug: 599326
|
|
|
|
|
| |
Package-Manager: portage-2.3.2
RepoMan-Options: --ignore-arches
|
|
|
|
|
|
| |
Package-Manager: portage-2.3.0
RepoMan-Options: --include-arches="x86"
Signed-off-by: Agostino Sarubbo <ago@gentoo.org>
|
|
|
|
|
|
| |
Package-Manager: portage-2.3.0
RepoMan-Options: --include-arches="amd64"
Signed-off-by: Agostino Sarubbo <ago@gentoo.org>
|
|
|
|
|
|
| |
Gentoo-Bug: 599326
Package-Manager: portage-2.3.0
|
|
|
|
|
|
| |
Gentoo-Bug: 599326
Package-Manager: portage-2.3.0
|
|
|
|
|
| |
Package-Manager: portage-2.3.2
RepoMan-Options: --include-arches="arm"
|
|
|
|
|
| |
Package-Manager: portage-2.3.2
RepoMan-Options: --ignore-arches
|
|
|
|
|
|
| |
Package-Manager: portage-2.3.0
RepoMan-Options: --include-arches="x86"
Signed-off-by: Agostino Sarubbo <ago@gentoo.org>
|
|
|
|
|
|
| |
Package-Manager: portage-2.3.0
RepoMan-Options: --include-arches="amd64"
Signed-off-by: Agostino Sarubbo <ago@gentoo.org>
|
|
|
|
|
| |
Package-Manager: portage-2.3.2
RepoMan-Options: --ignore-arches
|
|
|
|
| |
Package-Manager: portage-2.3.2
|
|
|
|
| |
Package-Manager: portage-2.3.2
|
|
|
|
| |
Package-Manager: portage-2.3.2
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We create several copies of ${S} -- one for each SAPI -- during the
build. Until now, those copies have been made with "cp -r". I believe
this caused unnecessary regeneration of the Zend parsers, opening the
door for version mismatches of sys-devel/bison.
For example, the file
${S}/Zend/zend_language_parser.c
is generated from
${S}/Zend/zend_language_parser.y,
but the ".c" file should already exist in the source tree. In the
upstream tarball, the former always exists (pre-generated) and has a
timestamp later than the latter. This prevents the build system from
attempting to call "yacc" on zend_language_parser.y. When we use
"cp -r" to copy the source tree, I find timestamps like the following:
2016-08-16 19:08 zend_language_parser.c
2016-08-16 19:08 zend_language_parser.y
They look identical, but if the copy was performed in alphabetical
order, I suspect that the ".y" file looks newer than the ".c" file
that it generates. It is therefore my educated guess that the build
system is using bison to regenerate those ".c" files when in fact
there is no need to do so. By using "cp -a" instead of "cp -r", I
hope to preserve the ages of those files, and eliminate bison from
normal end-user builds of dev-lang/php.
The fix has been applied to the latest 5.6 and 7.0 revisions in-place.
Gentoo-Bug: 595792
Package-Manager: portage-2.3.0
|
|
|
|
| |
Package-Manager: portage-2.3.0
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The main license under which PHP is distributed is the "PHP license."
But, a lot of files, functions, and libraries have been inlined and
bring with them the associated license from the upstream project. This
commit adds the following unconditionally:
* BSD (thread-safe resource manager, probably other places)
* Zend-2.0 (used by the Zend engine, everything under ${S}/Zend/)
and the following USE-conditionally:
* LGPL-2.1+, used by the bcmath extension.
* BSD-2, used by the fpm SAPI and mbstring extension.
* gd, used by gd.
* LGPL-2.1, used by the mbstring extension.
The main license was also updated from "PHP-3" to "PHP-3.01", because
that's what it is.
Package-Manager: portage-2.3.0
|