| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
Closes: https://github.com/gentoo/gentoo/pull/16762
Package-Manager: Portage-2.3.103, Repoman-2.3.23
Signed-off-by: Michael Mair-Keimberger <m.mairkeimberger@gmail.com>
Signed-off-by: Kent Fredric <kentnl@gentoo.org>
|
|
|
|
|
| |
Package-Manager: Portage-2.3.99, Repoman-2.3.23
Signed-off-by: Andreas K. Hüttel <dilfridge@gentoo.org>
|
|
|
|
|
| |
Package-Manager: Portage-2.3.99, Repoman-2.3.23
Signed-off-by: Andreas K. Hüttel <dilfridge@gentoo.org>
|
|
|
|
|
|
|
|
|
|
|
|
| |
- One instance of MissingSlash which pukes its brains over, thanks EAPI7
- Seven instances of unnecessary slash stripping
I suspect the fixes I do for the slash-stripping might later barf about
not adding an explict slash, which will be bonkers if that happens,
because the variables in question have leading slashes! Joys.
Package-Manager: Portage-2.3.100, Repoman-2.3.22
Signed-off-by: Kent Fredric <kentnl@gentoo.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is a work in-progress experiment, hence, it is unkeyworded until
I can get more eyes on the changes, and fully test the consequences at
scale.
Important Changes:
- Convert to EAPI7
- Remove inherit on eutils
- Replace calls to "epatch" to "eapply", but resulting in a loss of
nice output
- Add new hidden feature PERL_SINGLE_SLOT, which, when set, installs
perl into a directory named after SUBSLOT (eg: 5.30) as opposed to one
following the explicit name (eg: 5.30.2), which aims to pre-emptively
solve (in both direction) the problem faced by shipping binpkg's,
where the built perl has only one set of INC dirs (eg: 5.30.2), but a
binpkg was built with a different, but compatible perl (eg: 5.30.1),
and subsequently, installs to an @INC dir that is not visible to the
built perl. Instead, all perl's that are defined to be
inter-compatible share the same directory for both arch-dependent and
arch-independent code, so binpkg's only need to be regenerated when:
- Upgrading/downgrading between major revisions
- Flipping USE="debug" or USE="ithreads".
Under PERL_SINGLE_SLOT, directories that should be compatible, and are
available, but built under the previous scheme, are also inhaled into
@INC for ease of transition.
The name of this flag is subject to change, and may become a USE flag.
- Add a new hidden feature PERL_SUPPORT_SINGLE_SLOT, which builds perl
the same way as in previous versions, but also probes for version'd
directories generated by installing packages on perl's built with
PERL_SINGLE_SLOT, as a fallback mechaism for transitioning away from a
perl built with PERL_SINGLE_SLOT.
The name of this flag is subject to change, and may become a USE flag
- Add a patch to various parts of Configure, perl.c, and friends, to
facilitate the above, which exposes itself as -Dgentoolibdirs=, and
has the same syntax as -Dotherlibdirs, but doesn't pollute everything
by adding its own arch-dirs when they weren't asked for. This patch
may also later help facilitate building perl's without
PERL_SINGLE_SLOT, but with other @INC dirs forced into place, for the
same purpose, but implemented differently, as the previous mechanism,
-Dinc_version_list is limited in that it:
- Excludes internally directories that don't exist
- Mangles directories sometimes trashing @INC entirely, throwing
away litterally all the versions you passed.
- Fixed a very embarrasing typo in the einfo code, ${EROO%/T} ...
- Restructured the @INC discovery/cleanup logic into dedicated functions
- Add more error handling in the discovery path, especially adding loud
error output if directories that *need* to be traversed for compat
discovery cannot be traversed, due to misconfigured permissions.
- Fix an embarrasing bug in @INC list stripping, that due to inherently
being a *substring* match, not a *fullstring* match, could have
excluded 5.30.20 from the @INC path for 5.30.2, even though they're
intercompatible. This became more obvious, when one was trying to
strip '5.30' from a list that contained '5.30.1', '5.30.2', because it
just ate everything!
Questions:
- Why do we have bzip2 in RDEPEND? Surely, that should be BDEPEND-only
- Are we even using bzip2 anymore?
- Should we migrate the patch ball to being a more-common-these-days set
of numerically ordered patches, and potentially reduce the handling
complexity in the ebuild as a result?
Package-Manager: Portage-2.3.100, Repoman-2.3.22
Signed-off-by: Kent Fredric <kentnl@gentoo.org>
|
|
|
|
|
|
|
| |
Package-Manager: Portage-2.3.100, Repoman-2.3.22
Signed-off-by: Michael Mair-Keimberger <m.mairkeimberger@gmail.com>
Closes: https://github.com/gentoo/gentoo/pull/16231
Signed-off-by: Aaron Bauman <bman@gentoo.org>
|
|
|
|
|
| |
Bug: https://bugs.gentoo.org/685660
Signed-off-by: Mike Gilbert <floppym@gentoo.org>
|
|
|
|
|
|
|
| |
Package-Manager: Portage-2.3.99, Repoman-2.3.22
RepoMan-Options: --include-arches="hppa"
Signed-off-by: Rolf Eike Beer <eike@sf-mail.de>
Signed-off-by: Sergei Trofimovich <slyfox@gentoo.org>
|
|
|
|
|
|
| |
Package-Manager: Portage-2.3.99, Repoman-2.3.22
RepoMan-Options: --include-arches="x86"
Signed-off-by: Agostino Sarubbo <ago@gentoo.org>
|
|
|
|
|
|
| |
Package-Manager: Portage-2.3.99, Repoman-2.3.22
RepoMan-Options: --include-arches="s390"
Signed-off-by: Agostino Sarubbo <ago@gentoo.org>
|
|
|
|
|
|
| |
Package-Manager: Portage-2.3.99, Repoman-2.3.22
RepoMan-Options: --include-arches="ppc64"
Signed-off-by: Agostino Sarubbo <ago@gentoo.org>
|
|
|
|
|
|
| |
Package-Manager: Portage-2.3.99, Repoman-2.3.22
RepoMan-Options: --include-arches="ppc"
Signed-off-by: Agostino Sarubbo <ago@gentoo.org>
|
|
|
|
|
|
| |
Package-Manager: Portage-2.3.99, Repoman-2.3.22
RepoMan-Options: --include-arches="arm"
Signed-off-by: Agostino Sarubbo <ago@gentoo.org>
|
|
|
|
|
|
|
| |
Package-Manager: Portage-2.3.99, Repoman-2.3.22
RepoMan-Options: --include-arches="sparc"
Signed-off-by: Rolf Eike Beer <eike@sf-mail.de>
Signed-off-by: Sergei Trofimovich <slyfox@gentoo.org>
|
|
|
|
|
| |
Package-Manager: Portage-2.3.99, Repoman-2.3.22
Signed-off-by: Andreas K. Hüttel <dilfridge@gentoo.org>
|
|
|
|
|
|
| |
Bug: https://bugs.gentoo.org/723792
Package-Manager: Portage-2.3.99, Repoman-2.3.22
Signed-off-by: Andreas K. Hüttel <dilfridge@gentoo.org>
|
|
|
|
|
|
| |
Package-Manager: Portage-2.3.99, Repoman-2.3.22
Signed-off-by: Sam James (sam_c) <sam@cmpct.info>
Signed-off-by: Mart Raudsepp <leio@gentoo.org>
|
|
|
|
|
|
| |
Bug: https://bugs.gentoo.org/723792
Package-Manager: Portage-2.3.99, Repoman-2.3.22
Signed-off-by: Andreas K. Hüttel <dilfridge@gentoo.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
While this won't fix the warnings about hints/linux.sh, as that is
something too complex for me to trivially fix, it should mitigate the
warnings about nm and cpp, and additonally, guards against a possible
future where ranlib is also nuked and later tried to be used from
$Config{ranlib}
-r bump for compile propagation reasons, real delta:
--- a/dev-lang/perl/perl-5.30.2-r1.ebuild
+++ b/dev-lang/perl/perl-5.30.2-r2.ebuild
@@ -502,11 +502,16 @@ src_configure() {
# allow fiddling via EXTRA_ECONF, bug 558070
eval "local -a EXTRA_ECONF=(${EXTRA_ECONF})"
+ # setting -Dld= to tc-getLD breaks perl and all perl things
+ # https://github.com/Perl/perl5/issues/17791#issuecomment-630145202
myconf \
-Duseshrplib \
-Darchname="${myarch}" \
-Dcc="$(tc-getCC)" \
-Dar="$(tc-getAR)" \
+ -Dnm="$(tc-getNM)" \
+ -Dcpp="$(tc-getCPP)" \
+ -Dranlib="$(tc-getRANLIB)" \
-Doptimize="${CFLAGS}" \
-Dldflags="${LDFLAGS}" \
-Dprefix="${EPREFIX}"'/usr' \
Bug: https://bugs.gentoo.org/723734
Bug: https://github.com/Perl/perl5/issues/17791#issuecomment-630123559
Package-Manager: Portage-2.3.99, Repoman-2.3.22
Signed-off-by: Kent Fredric <kentnl@gentoo.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This one neat trick convinces ./configure to use a correct, and
specified "ar" during configure, as auto-detection completely fails
when there is no binary named "ar" in $PATH, and despite completely
failing to detect any "ar", configure just warns, and continues as
normal, and then hardcodes that total failure of detection in
Config_heavy.pl, indicating "hey, the 'ar' perl was built with was
'ar'", despite no such thing existing, and code afterwards will then
try ( and fail ) to use that `ar` by consulting $Config{ar}
This step compeletely side-steps auto-detection, so at very least,
Config_heavy.pl contains a value that at least one time, probably
worked, and as a result, large amounts of EUMM/MB XS stuff no longer
tries to use a default `ar` that never existed.
-r1 bump required, as the consequences of this change propagate into
everything that compiles C code against Perl, and a failure to upgrade
perl with this fix results in future failures compiling other stuff
But otherwise this really is just a one line fix:
```diff
--- perl-5.30.2.ebuild 2020-04-13 01:31:59.268561073 +1200
+++ perl-5.30.2-r1.ebuild 2020-05-18 16:46:13.972962817 +1200
@@ -507,4 +507,5 @@
-Darchname="${myarch}" \
-Dcc="$(tc-getCC)" \
+ -Dar="$(tc-getAR)" \
-Doptimize="${CFLAGS}" \
-Dldflags="${LDFLAGS}" \
```
Bug: https://bugs.gentoo.org/723264
Bug: https://bugs.gentoo.org/723154
Bug: https://github.com/Perl/perl5/issues/17791
Package-Manager: Portage-2.3.99, Repoman-2.3.22
Signed-off-by: Kent Fredric <kentnl@gentoo.org>
|
|
|
|
|
|
|
|
|
| |
m68k and ~m68k trees are inconsistent. Let's drop keywords
down to ~m68k only. Profiles already accept both keywords:
ACCEPT_KEYWORDS="m68k ~m68k"
Signed-off-by: Sergei Trofimovich <slyfox@gentoo.org>
|
|
|
|
|
| |
Package-Manager: Portage-2.3.89, Repoman-2.3.20
Signed-off-by: Andreas K. Hüttel <dilfridge@gentoo.org>
|
|
|
|
|
| |
Package-Manager: Portage-2.3.89, Repoman-2.3.20
Signed-off-by: Andreas K. Hüttel <dilfridge@gentoo.org>
|
|
|
|
|
|
|
|
| |
run/locale.t test fails, but this is *not* a regression from 5.30.1
See also https://github.com/Perl/perl5/issues/17713
Package-Manager: Portage-2.3.89, Repoman-2.3.20
Signed-off-by: Andreas K. Hüttel <dilfridge@gentoo.org>
|
|
|
|
| |
Signed-off-by: Matt Turner <mattst88@gentoo.org>
|
|
|
|
|
|
| |
Package-Manager: Portage-2.3.89, Repoman-2.3.20
RepoMan-Options: --ignore-arches
Signed-off-by: Mikle Kolyada <zlogene@gentoo.org>
|
|
|
|
|
|
|
| |
sys-freebsd/freebsd-mk-defs was removed from ::gentoo in October 2019.
Package-Manager: Portage-2.3.94, Repoman-2.3.21
Signed-off-by: Sergei Trofimovich <slyfox@gentoo.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Perl's Configure detected gcc-10 as gcc-1 and applied
-fpcc-struct-return option that breakw C ABI. This caused
mini-interpreter to crash early at bootstrap time.
The change is a direct backport of upstreams
6bd6308fcea3541e50565 ("Adapt Configure to GCC version 10").
Closes: https://bugs.gentoo.org/708744
Package-Manager: Portage-2.3.94, Repoman-2.3.21
Signed-off-by: Sergei Trofimovich <slyfox@gentoo.org>
|
|
|
|
| |
Signed-off-by: David Seifert <soap@gentoo.org>
|
|
|
|
|
|
|
| |
Update the copyright notice on all files that were touched since
January 1st but did not have the notice updated.
Signed-off-by: Michał Górny <mgorny@gentoo.org>
|
|
|
|
|
| |
Package-Manager: Portage-2.3.78, Repoman-2.3.17
Signed-off-by: Andreas K. Hüttel <dilfridge@gentoo.org>
|
|
|
|
| |
Signed-off-by: Matt Turner <mattst88@gentoo.org>
|
|
|
|
|
| |
Signed-off-by: Aaron Bauman <bman@gentoo.org>
Package-Manager: Portage-2.3.81, Repoman-2.3.20
|
|
|
|
|
| |
Package-Manager: Portage-2.3.78, Repoman-2.3.17
Signed-off-by: Andreas K. Hüttel <dilfridge@gentoo.org>
|
|
|
|
|
|
| |
Package-Manager: Portage-2.3.79, Repoman-2.3.16
RepoMan-Options: --include-arches="m68k"
Signed-off-by: Mikle Kolyada <zlogene@gentoo.org>
|
|
|
|
|
|
| |
Package-Manager: Portage-2.3.79, Repoman-2.3.16
RepoMan-Options: --include-arches="sh"
Signed-off-by: Mikle Kolyada <zlogene@gentoo.org>
|
|
|
|
|
|
| |
Package-Manager: Portage-2.3.79, Repoman-2.3.16
RepoMan-Options: --include-arches="s390"
Signed-off-by: Mikle Kolyada <zlogene@gentoo.org>
|
|
|
|
|
|
| |
Package-Manager: Portage-2.3.79, Repoman-2.3.16
RepoMan-Options: --include-arches="hppa"
Signed-off-by: Mikle Kolyada <zlogene@gentoo.org>
|
|
|
|
|
|
| |
Package-Manager: Portage-2.3.79, Repoman-2.3.16
RepoMan-Options: --include-arches="sparc"
Signed-off-by: Mikle Kolyada <zlogene@gentoo.org>
|
|
|
|
|
|
| |
Package-Manager: Portage-2.3.79, Repoman-2.3.16
RepoMan-Options: --include-arches="ia64"
Signed-off-by: Mikle Kolyada <zlogene@gentoo.org>
|
|
|
|
|
|
| |
Package-Manager: Portage-2.3.79, Repoman-2.3.16
RepoMan-Options: --include-arches="alpha"
Signed-off-by: Mikle Kolyada <zlogene@gentoo.org>
|
|
|
|
|
|
| |
Package-Manager: Portage-2.3.79, Repoman-2.3.16
RepoMan-Options: --include-arches="arm"
Signed-off-by: Mikle Kolyada <zlogene@gentoo.org>
|
|
|
|
|
|
| |
Package-Manager: Portage-2.3.79, Repoman-2.3.16
RepoMan-Options: --include-arches="ppc64"
Signed-off-by: Mikle Kolyada <zlogene@gentoo.org>
|
|
|
|
|
|
| |
Package-Manager: Portage-2.3.79, Repoman-2.3.16
RepoMan-Options: --include-arches="ppc"
Signed-off-by: Mikle Kolyada <zlogene@gentoo.org>
|
|
|
|
|
|
| |
Package-Manager: Portage-2.3.79, Repoman-2.3.16
RepoMan-Options: --include-arches="x86"
Signed-off-by: Mikle Kolyada <zlogene@gentoo.org>
|
|
|
|
|
|
| |
Package-Manager: Portage-2.3.79, Repoman-2.3.16
RepoMan-Options: --include-arches="amd64"
Signed-off-by: Mikle Kolyada <zlogene@gentoo.org>
|
|
|
|
|
| |
Package-Manager: Portage-2.3.79, Repoman-2.3.18
Signed-off-by: Andreas K. Hüttel <dilfridge@gentoo.org>
|
|
|
|
|
| |
Package-Manager: Portage-2.3.78, Repoman-2.3.17
Signed-off-by: Andreas K. Hüttel <dilfridge@gentoo.org>
|
|
|
|
|
| |
Package-Manager: Portage-2.3.78, Repoman-2.3.17
Signed-off-by: Andreas K. Hüttel <dilfridge@gentoo.org>
|
|
|
|
|
|
| |
Bug: https://bugs.gentoo.org/685660
Package-Manager: Portage-2.3.77, Repoman-2.3.17
Signed-off-by: Andreas K. Hüttel <dilfridge@gentoo.org>
|