Get Gentoo!
gentoo.org sites
gentoo.org Wiki Bugs Forums Packages
Planet Archives Sources
Infra Status
summaryrefslogtreecommitdiff
path: root/eclass
Commit message (Collapse)AuthorAgeFilesLines
* flag-o-matic.eclass: Strip LDFLAGS unsupported by the C compiler, #621274Michał Górny2017-08-252-1/+4
| | | | | | | | Include LDFLAGS in the variables stripped by strip-unsupported-flags. The code reuses the current functions for testing CC, and so only remove LDFLAGS that are rejected by the C compiler and not the linker. This solves the case of bug #621274 where LDFLAGS contained GCC-specific -flto flag.
* flag-o-matic.eclass: test-flag-PROG, ignore unused args in clangMichał Górny2017-08-252-1/+13
| | | | | | | | | | | | | | | | | | | By default, clang considers unused arguments as error when -Werror is used. Since flag tests are performed without linking, this causes all tests for linker flags to fail inadvertently and all those flags are stripped as a result. While the correctness of passing unused flags is doubtful, silently stripping them in a few random packages is certainly not the solution to the problem, and also makes the results differ between gcc and clang. To account for that, use clang's -Qunused-arguments option to silence unused argument warnings. To avoid wasting time on testing the compiler, just try passing -Qunused-arguments every time a flag check fails. If clang is not used, the additional call will fail just the same as the previous one (either because of the original flag or because of -Qunused-arguments), so the result will be the same.
* flag-o-matic.eclass: test-flag-PROG, refactor to reduce duplicationMichał Górny2017-08-251-3/+7
|
* git-r3.eclass: Explicitly warn about unsecure protocolsMichał Górny2017-08-251-1/+11
| | | | | | | Explicitly warn about any URI that uses an unsecure protocol (git, http) even if it's a fallback URI. This is necessary because an attacker may block HTTPS connections, effectively forcing the fallback to the unsecure protocol.
* git-r3.eclass: Update docs to discourage unsafe protocolsMichał Górny2017-08-251-6/+10
|
* myspell-r2.eclass: [QA] Use relative symlink target(s)Michał Górny2017-08-221-4/+4
|
* mozcoreconf-v5.eclass: change 'eval unset' to 'unset'Lars Wendler2017-08-221-1/+1
|
* xdg-utils.eclass: fix xdg_desktop_database_update function doc typoTim Harder2017-08-211-1/+1
|
* eclass/ruby-ng.eclass: mark ruby21 as a removed targetHans de Graaff2017-08-201-1/+1
|
* xorg-2.eclass: Fix EGIT_REPO_URI, #628226Michał Górny2017-08-191-1/+1
|
* Since I now have an @gentoo.org address, use it everywhereCraig Andrews2017-08-181-1/+1
| | | | | Gentoo-bug: 620766 Closes: #5470
* kde5*.eclass: Revert KDEBASE=kdel10n cleanupAndreas Sturmlechner2017-08-172-0/+113
| | | | | | We need to wait until removal of the package. This reverts commit edca947c05c8f83ab1bfd776bf3ea5e629609972.
* kde5*.eclass: KDEBASE=kdel10n cleanupAndreas Sturmlechner2017-08-172-113/+0
|
* kde5.eclass: KDE_TEST=forceoptional-recursive reloadedAndreas Sturmlechner2017-08-171-11/+31
| | | | | | | | | | | Searches for test subdirectory pattern in CMakeLists.txt recursively, enclose it with BUILD_TESTING conditional. Creates unified diff to easily pick up for cosmetics and submission upstream. Re-order unconditional Frameworks tests disabling to produce more compatible forceoptional-recursive tests.
* kde5-functions.eclass: Raise >=KF-5.37 QT_MINIMAL to 5.7.1Andreas Sturmlechner2017-08-171-4/+3
| | | | Raise PLASMA_MINIMAL to 5.10.4.
* kde4-base.eclass: Add {QT3SUPPORT,SQL}_REQUIREDAndreas Sturmlechner2017-08-171-13/+56
| | | | This makes dev-qt/qtsql:4 and dev-qt/qt3support:4 optional.
* xdg-utils.eclass: use HTTPS for freedesktop.orgDavid Hicks2017-08-171-1/+1
| | | | Package-Manager: Portage-2.3.6, Repoman-2.3.3
* systemd.eclass: use HTTPS for freedesktop.orgDavid Hicks2017-08-171-3/+3
| | | | Package-Manager: Portage-2.3.6, Repoman-2.3.3
* xorg-2.eclass: use HTTPS for freedesktop.orgDavid Hicks2017-08-171-2/+2
| | | | Package-Manager: Portage-2.3.6, Repoman-2.3.3
* x-modular.eclass: use HTTPS for freedesktop.orgDavid Hicks2017-08-171-2/+2
| | | | Package-Manager: Portage-2.3.6, Repoman-2.3.3
* mozconfig-v6.55.eclass: Adjusted libpng dependency (bug #628088).Lars Wendler2017-08-171-1/+1
|
* vala.eclass: allow vala 0.36Gilles Dartiguelongue2017-08-151-1/+1
|
* llvm.eclass: Do not prepend /usr/bin to PATH, #622866Michał Górny2017-08-121-1/+7
|
* llvm.eclass: Support checking LLVM deps via llvm_check_deps()Michał Górny2017-08-121-15/+45
| | | | | | | | Introduce the support for llvm_check_deps() function to override the default LLVM slot acceptance test (checking whether sys-devel/llvm is installed). This can be used to match more complex dependency specifications, e.g. to find a LLVM slot that has a matching clang version, or to request USE dependencies on LLVM or clang.
* llvm.eclass: Check for installed package rather than executableMichał Górny2017-08-121-7/+6
| | | | | | | | | Ensure that a specific LLVM slot is installed via using has_version on "sys-devel/llvm:${SLOT}" rather than checking whether llvm-config is installed in expected location. While it is a bit slower, this is closer to a canonical way of testing it and will be useful when we allow testing for more specific dependency strings. Right now, it could be helpful if one has broken LLVM installation (i.e. stray files).
* kde5-meta-pkg.eclass: Block slot 4 unconditionallyAndreas Sturmlechner2017-08-121-1/+1
| | | | This eclass has always been unaware of KDE_BLOCK_SLOT4.
* Revert "kde5-meta-pkg.eclass: Block slot 4 unconditionally"Andreas Sturmlechner2017-08-121-1/+1
| | | | This reverts commit 92c7fa972f87370dea450132ac6629dc7d514871.
* kde5-functions.eclass: Raise >=KF-5.37 QT_MINIMAL to 5.7.1Andreas Sturmlechner2017-08-121-1/+3
| | | | | See also: https://mail.kde.org/pipermail/release-team/2017-August/010526.html
* kde4-base.eclass: Drop obsolete kde-base/*:4 blockerAndreas Sturmlechner2017-08-121-4/+0
| | | | No ebuilds of this type should exist at this point after pkgmoves done.
* kde4-base.eclass: Drop obsolete USE conflict mitigationAndreas Sturmlechner2017-08-121-8/+1
|
* kde4-base.eclass: Drop obsolete minimum GCC checkAndreas Sturmlechner2017-08-121-11/+1
|
* kde5-functions.eclass: Drop 5.9999 version dep exceptionAndreas Sturmlechner2017-08-121-6/+1
|
* kde5-meta-pkg.eclass: Block slot 4 unconditionallyAndreas Sturmlechner2017-08-121-1/+1
| | | | This eclass has always been unaware of KDE_BLOCK_SLOT4.
* mysql-multilib-r1.eclass: Update system options for fatal comparison bug 627568Brian Evans2017-08-111-2/+2
|
* bzr.eclass: Dump to maintainer-neededMichał Górny2017-08-111-2/+2
|
* apache-2.eclass: don't enable maintainer-mode with USE=debug.Michael Orlitzky2017-08-111-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | The --enable-maintainer-mode flag serves two purposes: first, it enables compile-time warnings; and second, it forces all compiled modules to be loaded at runtime. To achieve the first goal, the build system checks for the "-std=c89" compiler flag and appends it to CFLAGS if found. This can cause a problem later, because the CFLAGS used to build apache are used by apxs to build extension modules. In particular, if you have an extension that relies on C99 or some later standard, and if apache was built with --enable-maintainer-mode, then apxs will attempt to build that extension according to C89 and fail. This failure can be observed in in bugs 621686, 621756, and 621794 when apache is built with USE=debug, because USE=debug sets the --enable-maintainer-mode flag. Since there is not much reason for an end user to enable maintainer- mode, the simplest fix for this is the wholesale removal of the --enable-maintainer-mode flag from USE=debug. This prevents us from having to append CFLAGS to each extension package that uses a later standard, or from having to add a USE dependency forbidding USE=debug in apache (which would create conflicts with e.g. mod_backtrace). Gentoo-Bug: 621686 Gentoo-Bug: 621756 Gentoo-Bug: 621794
* flag-o-matic.eclass: Revert "Strip LDFLAGS unsupported by the C..."Michał Górny2017-08-112-4/+1
| | | | | | | The current logic strips too much, causing build failures. Revert it until we get it right. Bug: https://bugs.gentoo.org/627474
* libtool.eclass: Use external eltpatch toolMichał Górny2017-08-111-471/+6
| | | | Closes: https://github.com/gentoo/gentoo/pull/4467
* toolchain.eclass: fix tc-enables-* with -ggdb3Luke Dashjr2017-08-101-4/+4
| | | | | | | | | | | | | | -ggdb3 builds debug information for macros into binaries. For this reason, the C preprocessor includes all #defines as-is in the output. The check in tc-enables-* expects only a fixed output of "true", which fails in this scenario. To fix this, `grep` is used to look specifically for "true" in the output from the preprocessor. Closes: https://github.com/gentoo/gentoo/pull/5359 Signed-off-by: Sergei Trofimovich <slyfox@gentoo.org> Signed-off-by: Matthias Maier <tamiko@gentoo.org>
* flag-o-matic.eclass: Strip LDFLAGS unsupported by the C compiler, #621274Michał Górny2017-08-082-1/+4
| | | | | | | | Include LDFLAGS in the variables stripped by strip-unsupported-flags. The code reuses the current functions for testing CC, and so only remove LDFLAGS that are rejected by the C compiler and not the linker. This solves the case of bug #621274 where LDFLAGS contained GCC-specific -flto flag.
* eclass/tests: Fix inheriting multiple eclassesMichał Górny2017-08-081-2/+2
| | | | | | Fix the inherit function to correctly handle 'inherit' call with multiple eclasses, instead of returning after the first eclass is successfully sourced.
* toolchain-glibc.eclass: fix libm.so symlinking for live glibcSergei Trofimovich2017-08-081-2/+6
| | | | | | | | | | | | | | | The failure happens when live glibc-9999 ebuild is installed: * QA Notice: Missing gen_usr_ldscript for libm-2.26.90.so * ERROR: sys-libs/glibc-9999::gentoo failed: * add those ldscripts The problem here is how upstream glibc version is detected: dosym ../../$(get_libdir)/libm-${PV}.so $(alt_usrlibdir)/libm-${PV}.so Change to use 'version.h' to pick upstream version. Signed-off-by: Sergei Trofimovich <slyfox@gentoo.org> Signed-off-by: Matthias Maier <tamiko@gentoo.org>
* eclass/mozconfig-v6.5{2,5} - Enable sandbox content on esr builds, majorJory A. Pratt2017-08-072-0/+385
| | | | changes for release build eclass
* java-pkg-opt-2.eclass: fix EAPI 6 support in java-pkg-opt-2_src_prepareAndrew Savchenko2017-08-071-0/+4
| | | | | | | | | | | | For EAPI 6+ java-pkg-opt-2_src_prepare() has eapply_user call via java-utils-2_src_prepare() from java-utils-2.eclass. But java-utils-2_src_prepare() call is conditional and in case when package is build with USE=-java java-utils-2_src_prepare() is not called, hence eapply_user is not called in src_prepare phase and ebuild fails. This problem is fixed by calling eapply_user if java USE is disabled _and_ EAPI is 6+.
* toolchain.eclass: upstream now uses .xz compressed tarballsAnthony G. Basile2017-08-031-2/+10
|
* opam.eclass: Allow to override package nameAlexis Ballier2017-08-021-4/+5
|
* opam.eclass: Initial import.Alexis Ballier2017-08-021-0/+49
|
* confutils.eclass: Remove last rited eclassMichał Górny2017-07-301-486/+0
|
* leechcraft.eclass: Always use HTTPS for accessing GitHubDavid Hicks2017-07-301-2/+1
| | | | | | | To prevent MITM attacks, always use HTTPS with GitHub domains. GitHub supports "Smart HTTPS" git which means that shallow clones are possible over HTTPS. Don't use a git:// fallback because this would allow an attacker to always force fallback to an unsafe protocol.
* bitcoincore.eclass: Always use HTTPS for accessing GitHubDavid Hicks2017-07-301-1/+1
| | | | | | | To prevent MITM attacks, always use HTTPS with GitHub domains. GitHub supports "Smart HTTPS" git which means that shallow clones are possible over HTTPS. Don't use a git:// fallback because this would allow an attacker to always force fallback to an unsafe protocol.