| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
| |
Recompressing tarball contents with XZ settings more carefully
constructed to avoid using SHA-256 integrity checks, which break
with app-arch/xz-utils[-extra-filters]
Output of tar -xOf <patcheset>.tar.xz | sha1sum should be the same.
Closes: https://bugs.gentoo.org/642124
Package-Manager: Portage-2.3.18, Repoman-2.3.6
|
|
|
|
|
|
|
| |
Unfortunately I ended up with a broken Perl (5.26.1) but this fix is
needed regardless.
Package-Manager: Portage-2.3.16, Repoman-2.3.6
|
|
|
|
|
|
|
| |
636370
Closes: https://bugs.gentoo.org/636370
Package-Manager: Portage-2.3.13, Repoman-2.3.4
|
|
|
|
| |
Package-Manager: Portage-2.3.13, Repoman-2.3.4
|
|
|
|
| |
Closes: https://github.com/gentoo/gentoo/pull/6074
|
|
|
|
| |
Package-Manager: Portage-2.3.8, Repoman-2.3.3
|
|
|
|
| |
Package-Manager: Portage-2.3.6, Repoman-2.3.2
|
|
|
|
| |
Package-Manager: Portage-2.3.6, Repoman-2.3.2
|
|
|
|
|
|
|
| |
This only affects cross-compiling perls, and then, makes cross-compile
work where previously expected not to.
Package-Manager: Portage-2.3.6, Repoman-2.3.2
|
|
|
|
| |
Package-Manager: Portage-2.3.5, Repoman-2.3.2
|
|
|
|
| |
Package-Manager: Portage-2.3.5, Repoman-2.3.2
|
|
|
|
| |
Package-Manager: Portage-2.3.5, Repoman-2.3.2
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Older bashes seem to think:
$(( "26" % 2 ))
Is
$(( ""26" % 2 " ))
Or something, and barfs.
Package-Manager: Portage-2.3.5, Repoman-2.3.2
|
|
|
|
| |
Package-Manager: Portage-2.3.5, Repoman-2.3.2
|
|
|
|
| |
Package-Manager: Portage-2.3.5, Repoman-2.3.2
|
|
|
|
| |
Package-Manager: Portage-2.3.5, Repoman-2.3.2
|
|
|
|
|
|
|
|
| |
This is a result of the oversight that PV contains _rc and DIST_VERSION
contains -RC, and this leads to the latter leaking into libpaths
and subslots, where it shouldn't.
Package-Manager: Portage-2.3.5, Repoman-2.3.2
|
|
|
|
|
|
|
|
|
|
| |
This is because we don't need to update the patches as often as perl
updates, because the patch set tends to be portable across versions.
This prevents us from needing a new patch tarball simply because we
changed version.
Package-Manager: Portage-2.3.5, Repoman-2.3.2
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
As per discussion on #gentoo-perl, this is slated as a strategy for
5.26, as it means people who upgrade to 5.26 retain existing installed
modules in their @INC
This serves as additional defence against portage build-order issues,
which are going to become especially pertinent given we're going to
have a substantial number of packages likely to fail configure or test.
So its important that people who can't rebuild packages can still have
existing versions continue to work on the newer perl where possible.
Package-Manager: Portage-2.3.5, Repoman-2.3.2
|
|
|
|
| |
Package-Manager: Portage-2.3.5, Repoman-2.3.2
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Development releases of Perl are not ABI-intercompatible with each
other, regardless of *actual* ABI compat, as Perl itself enforces
minor-version breaks in XS code.
Hence, this commit:
1. Ensures that development releases use the full 5.xx.yyy for the
subslot
2. Ensures the arch-abi-path from older 5.ODD series is not shared
with newer 5.ODD
Package-Manager: Portage-2.3.4, Repoman-2.3.2
|
|
|
|
| |
Package-Manager: Portage-2.3.4, Repoman-2.3.2
|
|
|
|
| |
Package-Manager: Portage-2.3.4, Repoman-2.3.2
|
|
This is a pre-release of 5.26 series and aims to be a
work-in-progress for the life of Perl 5.26.
Changes are intended to happen here first, and then get folded
out into actual releases.
This version requires grown-up mode and likely judicious use
of package.provided ( because at least at this time, requisite
virtuals are missing )
Also, this package is very ambitious and employs INC modifications
that incorporate a broader selection of previous perls' versions,
by re-including the architecture-independent paths from older
perls.
Its not known at this time if this is a viable strategy for a
final release, but it intends to make testing this easier.
( Because you might need lots of --nodeps to use this version
to begin with )
Also, you may want to borrow from
https://github.com/gentoo-perl/perl-testing-profiles
Which has a few things optimised for doing this, and for testing
in general, including some workarounds for known defects / spurious
failures.
Package-Manager: Portage-2.3.4, Repoman-2.3.2
|