- Use DIST_EXAMPLES logic
Upstream:
- Fix symlink attack from failure to check perltidy.ERR deletion
- Don't mis-parse certain anonymous hash references
- Don't parse => after __END__ or __DATA__ as quotes
- Fix parsing of perltidyrc
- Add support for <<>> operator.
- Fix --enc=utf8 + --backup-and-modify-in-place
- Fix minor formatting issue with one-line blocks with subs with sigs
- Fix utf8 error when output is STDOUT
- Improve spacing of try/catch/finally blocks
- Fix incorrect parsing of anon-subs with sigs and prototypes as
broken ternaries
- Add new open/closing block blank line controls
Package-Manager: Portage-2.3.5, Repoman-2.3.2
Upstream:
- Move author/release tests from install-side test paths
- List missing but required parameters in error message
Package-Manager: Portage-2.3.5, Repoman-2.3.2
- EAPI6
- Parallel Testing enabled
- DESCRIPTION fixed
Upstream:
- Add devicetype to service hashref
- Add support for port state ttl
Package-Manager: Portage-2.3.5, Repoman-2.3.2
Provide an alternate mode for python_setup() that behaves similarly to
python-any-r1 eclass. If python_check_deps() function is declared
by the ebuild, the python_setup logic switches to accepting any
implementation that is in PYTHON_COMPAT, installed and satisfies
python_check_deps() independently of USE flags.
This new logic makes it possible to replace some of the existing
REQUIRED_USE constraints for build-time dependencies with more friendly
any-of dependencies. For example, if a package supports both Python 2 &
Python 3 but has a purely Python 2 build-time dependency (e.g. for
building documentation) we had to force Python 2 being enabled via
REQUIRED_USE. Using python_check_deps() with appropriate any-of
dependency, we can use Python 2 for this task without actually forcing
the user to change USE flags or install the package for Python 2.
Inline the logic needed to iterate over implementations directly into
python_setup instead of using python_foreach_impl. This is mostly NFC,
except that we iterate in reverse order now -- that is, we start at
the newest implementation and stop at the first one that works for us.
Previously we (implicitly) started at the oldest implementation, checked
all implementation and used the last one (i.e. the newest) that worked.
More importantly, the new code makes it possible to alter the logic more
easily and avoid relying on implementation of python_foreach_impl().
Move the PYTHON_COMPAT_OVERRIDE warning from _python_obtain_impls()
to _python_validate_useflags(). Since the latter function is the only
point where the former is called, this is a purely cosmetic change at
the moment. However, it makes it possible to reuse the warning in
additional places without the necessity of setting MULTIBUILD_VARIANTS.
Rewrite the python_*_all() phase running code to reuse python_setup
instead of hacking on top of python_foreach_impl. The resulting code
is a bit simpler but most importantly, it avoids duplication of code
from python-r1 and ensures that distutils-r1 common phases are directly
altered by changes in python_setup.
The code still needs to reimplement some of the internals. However, it
is mostly limited to code specific to distutils-r1, and should be more
maintainable.
Make the pattern matching code in _python_impl_matches() more lax,
allowing (accidental) mixing of PYTHON_COMPAT-style values with
EPYTHON-style values. This is trivial to do, and solves the problem
introduced by complexity-by-limitation of other eclasses -- where
patterns for dependency strings are using PYTHON_COMPAT syntax,
and patterns for python_setup are using EPYTHON syntax.
- EAPI6
- Parallel Tests
Upstream:
- Make names of pseudo-anonymous generated roles read similar to
parameterized role name for better debug output
- Add stub node MooseX::Role::Parameterised for ease of discovery
Package-Manager: Portage-2.3.5, Repoman-2.3.2
Upstream:
- Remove many previously advertised deprecated functions/interfaces
- Fix app generator command where config file name was not based on
application name
Package-Manager: Portage-2.3.5, Repoman-2.3.2
Upstream glib is converting COPYING to LGPL-2.1+ for next major
release, but meanwhile various individual files were already
claiming 2.1+, though some interpretation says COPYING is the
aggregate license.
Just pre-emptively change from LGPL-2+ to LGPL-2.1+ for us to
be on the safe side and not forget to do it later
Package-Manager: Portage-2.3.5, Repoman-2.3.2
nosetests was used for no reason. Replace with unittest, which requires
no external dependencies.
The test code was loading libcrack.so from the system libdir rather
than the freshly build library.
Package-Manager: Portage-2.3.6_p1, Repoman-2.3.2_p69
sys-apps/systemd may be moving from /usr/lib/systemd to /lib/systemd
in a future release. dracut will automatically call pkg-config at run
time if these paths are not in the config file.
Package-Manager: Portage-2.3.5_p31, Repoman-2.3.2_p61
Upstream:
- Reduce memory consumption
- Disable Queue barriers on Windows
- Fix tmp_file script path in ::Flock
- Use posix_exit for Curses and Prima
- Allow hashes as input_data for Core, Flow, Loop & Step
- Improve IPC and signal handling
- Make tmp_dir and sess_dir on demand.
- Load Fcntl, File::Path and Symbol on demand
Package-Manager: Portage-2.3.5, Repoman-2.3.2