Pkgcore

Latest version: v0.12.28

Safety actively analyzes 682387 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 24 of 27

0.3.3

--------------------------

- IUSE defaults are respected now, so EAPI=1 implemented

- Write slotted atoms to worldfile as portage supports this now

- Sync up with portage; add support for lzma to unpack- mirror r7991 from
portage.


--------------------------

0.3.2

--------------------------

- ticket 190746 from gentoo; basically need to force the perms of first level
directory of an unpacked $DISTDIR to ensure it's at least readable/writable.
fixes unpacking of app-misc/screen-4.0.3_p20070403::gentoo-x86 .

- ticket 118; if -u, don't add the node to world set.

- correct a corner case in python implementation of cpv comparison (just
python, cpy extension handles it correctly); bug 188449 in gentoo, basically
floats have a limited precision, thus it was possible to get truncation in
comparison with specially crafted versions.

- handle EOF/IOError on raw_input (for --ask) a bit more gracefully, ticket
108.

- cd to ${WORKDIR} if ${S} doesn't exist for test/install phases; matches
change in portage behaviour.

- Now require snakeoil version 0.2 and up- require new capability of
AtomicWriteFile, ability to specify uid/gid/perms. Via that, fixes ticket
109 (umask leaking through to profile.env).

- the 'glsa' pkgset is now deprecated in favor of 'vuln'; will remain
through till 0.4 (ticket 106).

- ticket 105/96; fix via andkit, basically a bug in einstall lead to
extra einstall opts getting dropped instead of passed through.

- compatibility fix for lha unpacking for nwere versions of lha.

- emake now invokes ${MAKE:-make}, instead of make- undocumented ebuild
req, see bug 186598 at bugs.gentoo.org.

- pmerge --verbose is now pmerge -F portage-verbose-formatter

- Stop installing pregen symlink; functionality moved to pmaint regen.

- 'pmerge --domain' was added; basically is a way to specify the domain to
use, else usees the configuration defined default domain.

- new ebuild trigger to avoid installing files into symlinked dir (get_libdir
is the friend to fix a common /usr/lib -> /usr/lib64 bug), ticket 119


--------------------------

0.3.1

--------------------------

- ticket 86; export FILE for portage_conf FETCHCOMMAND/RESUMECOMMAND support,
convert from spawn_bash to spawn, add some extra error detection

- Correct cleanup of unknown state ebp processors; basically discard them if
they fail in any way. Cleanup inherit error msg when under ebd.

- Correct permission issue for vdb virtuals cache.

- ticket 84; rework overlay internals so that sorting order can't accidentally
expose a version masked by a higher priority repository in an overlay stack.


------------------------

0.3

------------------------

- pregen has moved into pmaint regen.

- Several example scripts that show how to use the pkgcore api have been
added, among others:
- repo_list (lists repos and some of their attributes)
- changed_use (a poor man's --newuse)
- pkg_info (show maintainers and herds of a package)
- pclean (finds unused distfiles)

- Pkgcore now supports several different output formats for the buildplan.
Portage and Paludis emulation are the notable formats, though plan
category/package and the original output are also available as options.

- Portage formatter is now the default.

- Pkgcore formatter (no longer default) output was simplified to be less
noisy.

- Large grammar fixes for documentation.

- Miscellaneous pylint cleanups, including whitespace fixes.

- Most of pkgcore.util.* (mainly the non pkgcore-specific bits) have been
split out into a separate package, snakeoil. This includes the relevant cpy
extensions.

- Triggers are quieter about what they're doing by default.

- /etc/portage/package.* can now contain unlimited subdirectories and
files (ticket 71).

- livefs functionality is no longer accessible in pkgcore.fs.*; have to access
pkgcore.fs.livefs.*

- old style virtual providers from the vdb are now preferred for newer versions
over profile defined defaults.

- added profile package.use support.

- ticket 80; $REPO_LOC/profiles/categories awareness; if the file exists, the
repo uses it by default.

- resolver refactoring; report any regressions to ferringb. Integrated in
events tracking, so that the choices/events explaining the path the resolver
took are recorded- via this, we actually have sane "resolution failed due to"
messages, adding emerge -pt/paludis --show-reasons is doable without hacking
the resolver directly, spotting which pkgs need to be unmasked/keyworded for
a specific request to be satisfied, etc, all of it is doable without having
to insert code directly into the resolver. Anyone interested in adding these
featues, please talk to harring.
Worth noting, the events api and data structs for the resolver are still a
work in process- meaning the api is not guaranteed to stay stable at least
till the next minor release.

- old style virtual pkgs are no longer combined into one with multiple
providers; aside from simplifying things, this fixes a few annoying resolution
failures involving virtual/modutils.


---------------------------

0.2.14

---------------------------

- correct potential for profile path calculation screwup.

- refactor isolated-functions.sh so all internal vars are prefixed with
PKGCORE_RC\_; shift vars filter to PKGCORE_RC\_.* instead of RC\_.* .
If you were having problems building courier-imap (RC_VER variable),
this fixes it.

- better interop with paludis VDB environment dumps.

- treat RESTRICT as a straight depset for UI purposes (minor, but looks
better this way).


---------------------------

0.2.13

---------------------------

- Added '~' to allowed shlex word chars.

- Due to amd64 /lib -> /lib64, change the default policy for sym over
directory merging to allow it if the target was a directory.


---------------------------

Page 24 of 27

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.