| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
| |
Closes: https://github.com/gentoo/gentoo/pull/1826
Signed-off-by: Patrice Clement <monsieurp@gentoo.org>
|
|
|
|
|
|
| |
Closes: https://github.com/gentoo/gentoo/pull/1826
Signed-off-by: Patrice Clement <monsieurp@gentoo.org>
|
|
|
|
|
|
|
|
| |
Required for the upcoming mpv-0.17.0-r6 stabilization.
Closes: https://github.com/gentoo/gentoo/pull/1776
Signed-off-by: Yixun Lan <dlan@gentoo.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Backport patches for huge memleaks fixed after -r5 was added to the
tree. This revbump contains only very minor changes compared to -r5.
Thus there's no need to wait another 30 days prior to stabilization.
There will be no more revbumps for 0.17.0 because 0.18.0 is out and
this is the perfect time to stabilize 0.17.0.
Package-Manager: portage-2.3.0
Closes: https://github.com/gentoo/gentoo/pull/1776
Signed-off-by: Yixun Lan <dlan@gentoo.org>
|
|
|
|
|
|
| |
Bug: 585882
Package-Manager: portage-2.2.28
|
|
|
|
|
|
| |
Add ~arm keywording to 52c, and also fix up the Gentoo copyright.
Package-Manager: portage-2.3.0
|
|
|
|
| |
Package-Manager: portage-2.3.0
|
|
|
|
|
|
| |
vanilla-4.6.3 + genpatches-4.6-3 + grsecurity-3.1-4.6.3-201607060823
Package-Manager: portage-2.2.28
|
|
|
|
| |
Package-Manager: portage-2.2.28
|
|
|
|
|
|
|
|
| |
Also update to EAPI 6
Gentoo-Bug: https://bugs.gentoo.org/574082]
Package-Manager: portage-2.2.28
|
| |
|
|
|
|
| |
Package-Manager: portage-2.2.28
|
|
|
|
| |
Package-Manager: portage-2.2.28
|
|
|
|
| |
Package-Manager: portage-2.2.28
|
|
|
|
| |
Package-Manager: portage-2.2.28
|
|
|
|
| |
Package-Manager: portage-2.3.0
|
|
|
|
| |
Package-Manager: portage-2.3.0
|
|
|
|
| |
Package-Manager: portage-2.3.0
|
|
|
|
| |
Package-Manager: portage-2.3.0
|
|
|
|
| |
Package-Manager: portage-2.3.0
|
|
|
|
| |
Package-Manager: portage-2.3.0
|
|
|
|
| |
Package-Manager: portage-2.3.0
|
|
|
|
| |
Package-Manager: portage-2.3.0
|
|
|
|
| |
Package-Manager: portage-2.3.0
|
|
|
|
| |
Package-Manager: portage-2.3.0
|
|
|
|
|
|
|
| |
Bug: http://bugs.gentoo.org/588072
Bug: http://bugs.gentoo.org/587334
Package-Manager: portage-2.2.28
|
|
|
|
| |
Package-Manager: portage-2.2.28
|
|
|
|
|
|
| |
Bug: http://bugs.gentoo.org/581326
Package-Manager: portage-2.2.28
|
|
|
|
|
|
|
|
|
| |
This will be the new stable candidate
Bug: http://bugs.gentoo.org/588072
Bug: http://bugs.gentoo.org/587334
Package-Manager: portage-2.2.28
|
|
|
|
|
|
|
|
|
| |
HOST_CC and HOST_CXX are used to build tools like nsinstall which are needed
to install later on. Until now, these values were undefined and for whatever
reason were never autodetected to match the CHOST based tools. This commit
should resolve that issue.
Bug: http://bugs.gentoo.org/565124
|
|
|
|
|
|
| |
Bug: http://bugs.gentoo.org/585560
Package-Manager: portage-2.2.28
|
|
|
|
|
|
| |
Bug: http://bugs.gentoo.org/587334
Package-Manager: portage-2.2.28
|
|
|
|
|
|
|
|
|
|
| |
mozconfig
mozilla-48 and newer have dropped some configuration options that are no longer used
in the build system, and due to the way the new python configure operates, any options
specified that are not recognized are fatal. Moving these options out of mozcoreconf
allows the older mozconfig's to retain the same configuration while also allowing newer
mozconfig's to drop them as appropriate.
|
|
|
|
| |
Package-Manager: portage-2.3.0
|
|
|
|
| |
Package-Manager: portage-2.2.28
|
|
|
|
| |
Package-Manager: portage-2.3.0
|
| |
|
|
|
|
| |
Package-Manager: portage-2.3.0
|
|
|
|
|
|
|
|
| |
Also update to EAPI 6
Gentoo-Bug: https://bugs.gentoo.org/574082
Package-Manager: portage-2.2.28
|
|
|
|
|
|
|
|
| |
Also update to EAPI 6
Gentoo-Bug: https://bugs.gentoo.org/574082
Package-Manager: portage-2.2.28
|
|
|
|
| |
Package-Manager: portage-2.3.0
|
|
|
|
| |
Package-Manager: portage-2.3.0
|
|
|
|
|
|
| |
Gentoo-bug: 588180
Package-Manager: portage-2.3.0
|
|
|
|
| |
Package-Manager: portage-2.3.0
|
|
|
|
| |
Package-Manager: portage-2.3.0
|
| |
|
|
|
|
|
|
| |
1) 15.08.x has left the tree
2) Prepare for a future kde4-l10n without USE=minimal
Version block makes sure of no ancient kde4-l10n anyway
|
|
|
|
| |
is defined
|
|
|
|
|
| |
KDE_GCC_MINIMAL will now only be exported in packages that require it, as it
triggers an expensive pkg_pretend check whenever it is defined.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Exporting pkg_pretend is expensive, even if the exported function is a noop.
As kde5_pkg_pretend is currently only used to check if the active GCC version
is recent enough, only export that phase if it will have something to do.
The number of situations in which KDE_GCC_MINIMAL is exported will be
substantially reduced in a future commit. This will result in a large time
saving at the beginning of the emerge process as we will no longer see hundreds
of lines of:
>>> Running pre-merge checks for kde-foo/bar-123
>>> Running pre-merge checks for kde-foo/baz-123
|