| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Package-Manager: portage-2.2.26
|
|
|
|
| |
Package-Manager: portage-2.2.26
|
| |
|
|
|
|
|
|
| |
Gentoo-Bug: 573892
Package-Manager: portage-2.2.27
|
|
|
|
|
|
| |
Gentoo-Bug: 573892
Package-Manager: portage-2.2.27
|
|
|
|
| |
Package-Manager: portage-2.2.27
|
|
|
|
| |
Package-Manager: portage-2.2.27
|
|
|
|
| |
Package-Manager: portage-2.2.27
|
|
|
|
| |
Package-Manager: portage-2.2.27
|
|
|
|
| |
Package-Manager: portage-2.2.27
|
|
|
|
|
|
| |
has path breakage.
Package-Manager: portage-2.2.27
|
|
|
|
|
|
| |
The both wrappers were moved to /usr/bin in order to make it possible to
symlink them in place of /usr/bin/python{,2,3}. Compatibility symlinks
are now installed in place of old locations.
|
|
|
|
| |
Package-Manager: portage-2.2.27
|
| |
|
| |
|
|
|
|
|
|
| |
The new 2.3 release is the first release using new python-exec.conf
configuration file that allows users to specify complete Python
implementation preferences for python-exec.
|
|
|
|
|
|
| |
Fix eselect-ruby dependency to a new enough version that can handle ruby 2.3.
Package-Manager: portage-2.2.26
|
| |
|
| |
|
|
|
|
| |
Package-Manager: portage-2.2.27
|
|
|
|
|
|
| |
Python 2 preference is meaningless since we only support one version
of Python 2, and it causes Python 2 to be preferred over non-selected
versions of Python 3.
|
|
|
|
|
|
|
| |
Do not copy Python 2 version preference if Python 3 is the main
interpreter. It is not meaningful since we no longer support more than
one Python 2 version, and it will cause Python 2 to be preferred over
non-preferred versions of Python 3.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
Gentoo-Bug: 573892
Package-Manager: portage-2.2.26
|
| |
|
| |
|
|
|
|
|
|
| |
Gentoo-Bug: 463018
Package-Manager: portage-2.2.27
|
|
|
|
| |
Package-Manager: portage-2.2.27
|
|
|
|
| |
Package-Manager: portage-2.2.27
|
|
|
|
| |
Package-Manager: portage-2.2.27
|
|
|
|
| |
Package-Manager: portage-2.2.27
|
|\
| |
| |
| | |
Pull request: https://github.com/gentoo/gentoo/pull/732
|
| | |
|
| |
| |
| |
| | |
Package-Manager: portage-2.2.27
|
| |
| |
| |
| | |
Package-Manager: portage-2.2.27
|
| |
| |
| |
| | |
Package-Manager: portage-2.2.27
|
| | |
|
| |
| |
| |
| | |
Package-Manager: portage-2.2.27
|
| |
| |
| |
| | |
Package-Manager: portage-2.2.27
|
| |
| |
| |
| | |
Package-Manager: portage-2.2.27
|
|/
|
|
|
|
| |
Gentoo-Bug: 559924
Package-Manager: portage-2.2.27
|
|
|
|
|
|
|
|
|
|
| |
The interactive "php -a" command-line interface will hang unless PHP
is built with USE=readline. This used to be an elog warning, but was
rather easy to overlook and mysterious to those who hit the bug. We
already have REQUIRED_USE for our other flags, so it makes sense to
enforce the cli dependency on readline there.
Package-Manager: portage-2.2.26
|
|
|
|
|
|
|
|
| |
Now that PHP upstream is playing fast and loose with their versioning,
our slotting applies to major versions as well as minor ones. Remove
the word "minor" since it's no longer correct.
Package-Manager: portage-2.2.26
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We have two bugs (432962 and 572436) regarding stale eselect symlinks.
The first issue is that removal of an old slot does not update the
eselect-php symlinks to point to a newer slot. Thus, if a user
upgrades slots and depcleans the old one, his symlinks (and thus PHP)
are left broken until eselect-php is run manually. This is fixed by
running `eselect php cleanup` in pkg_postrm, since removal of the
old slot will trigger a cleanup (which updates the symlink).
The second issue is that disabling a SAPI would leave behind a broken
symlink. For example, if the "cgi" SAPI was once used but the user has
reinstalled PHP with USE="-cgi", then the old eselect-php symlink for
php-cgi would be left behind. This is fixed by running `eselect php
cleanup` in pkg_postinst, since that will be triggered after the
reinstall finishes, at which point the php-cgi symlink will be dead
and thus get removed.
Gentoo-Bug: 432962
Gentoo-Bug: 572436
Package-Manager: portage-2.2.26
|
|
|
|
|
|
|
|
|
|
| |
We had to leave db:5.3 out of our dependency string until now because
the upstream build system couldn't detect it. The latest v5.6.17 and
v7.0.2 will find it, though, so we add it as an option.
Gentoo-Bug: 564824
Package-Manager: portage-2.2.26
|
|
|
|
|
| |
Package-Manager: portage-2.2.26
Signed-off-by: Patrice Clement <monsieurp@gentoo.org>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
PHP has two Firebird drivers -- the legacy "interbase" driver and the
new pdo-firebird driver. We have always supported the legacy driver
with USE=firebird, but were missing the pdo-firebird configure flag
when USE="pdo firebird" was set. Similar tricks were in place for
e.g. sqlite and oci8, but Firebird was forgotten.
Dmitry A. Bakshaev was nice enough to point this out in bug 538226,
and even supplied a patch. Testing shows that both drivers work in
php:5.6, but that only the PDO driver works in php:7.0. That's not
a regression; this commit adds the only driver that works in php:7.0.
Gentoo-Bug: 538226
Suggested-By: Dmitry A. Bakshaev
Package-Manager: portage-2.2.26
|