| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
This only affects r'\w' with Python 2.x, since Python 3 already
defaults to re.UNICODE behavior when compiling unicode str objects
(unless re.ASCII is specified). If a repository wants to ban unicode
categore/package names then we can add a layout.conf setting for that,
as discussed in bug #435934.
|
|
|
|
|
|
|
|
|
| |
EAPI 5 supports automatic rebuilds via the slot-operator and sub-slots,
which makes preserve-libs much more user-friendly, since it makes
@preserved-rebuild unnecessary (also see bug #364425 for explanation of
@preserved-rebuild shortcomings). Therefore, enable preserve-libs for
the stable branch, but not by default. After EAPI 5 is widely adopted,
we can consider enabling preserve-libs by default.
|
|
|
|
|
| |
This will allow for the option to be available in the stable branch
without changing the default --depclean behavior.
|
| |
|
| |
|
|
|
|
|
| |
The fetch_symbol variable was always just a space, and no return value
was really needed.
|
|
|
|
|
| |
This is for reinstall due to slot or sub-slot change of a dependency
when the := slot operator is used.
|
|
|
|
|
| |
This should not change the behavior at all, but it makes the display
much easier to modify or extend.
|
|
|
|
|
|
| |
Also, make options like emerge --newuse ignore the state of USE=test,
since users typically don't want to trigger a bunch of rebuilds when
they enable or disable FEATURES=test.
|
|
|
|
|
|
|
|
|
| |
This is the default location used by current versions of eselect
profile, and will soon be the default location in stages. Since
eselect profile generates a warning if both /etc/make.profile and
/etc/portage/make.profile exist, the new default should be fairly
safe (although eselect profile currently prefers /etc/make.profile
when both exist).
|
|
|
|
| |
See bug #332217, comment #24.
|
| |
|
| |
|
|
|
|
| |
This will fix bug #332217.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
Now portage will unconditionally make a temporary copy of itself during
updates. This is safer, since it provides maximum protection against
any possible incompatibilities. For example, suppose that the ebuild
has been updated to change the location of installed files (such as
libdir change) without a revision bump.
|
|
|
|
|
|
|
|
| |
It's already been enabled by default in stable portage for awhile now,
so it should be safe to enable it unconditionally. The PMS eapi-5
branch also says that it's mandatory to parse the EAPI:
http://git.overlays.gentoo.org/gitweb/?p=proj/pms.git;a=commit;h=91d1e1e39b034bde7e5b981a5616a127135f37fa
|
|
|
|
|
| |
This makes it consistent with the language in the PMS eapi-5 branch:
http://git.overlays.gentoo.org/gitweb/?p=proj/pms.git;a=commit;h=5d6749ac9e5ddc5b1daaad7737b65fa81c6ece47
|
|
|
|
|
| |
See bug #176467 and the PMS patch:
http://git.overlays.gentoo.org/gitweb/?p=proj/pms.git;a=commit;h=d9040ab3482af5f790368bac5d053bf1cd760ba8
|
| |
|
| |
|
|
|
|
|
| |
See bug #354219 and the PMS patch:
http://git.overlays.gentoo.org/gitweb/?p=proj/pms.git;a=commit;h=1c2dff2df2305aff88a734e3a2716de1bb69f3b6
|
| |
|
|
|
|
|
| |
This will be needed in order to support stable use.mask/force for
bug #431078.
|
| |
|
|
|
|
|
| |
This fixes AttributeError exceptions for API consumers that override
sys.std* streams pseudo-file objects.
|
|
|
|
|
| |
Now any callable object will work, which might be helpful for
consumers of the Manifest.checkFileHashes() method.
|
| |
|
|
|
|
|
|
|
| |
This ensures that the code from commit
fe03b5fd790fc09bd6594c55bb174e80aaac1e5a behaves correctly even when
there are no poll events arriving for a long time (which might happen
if the running builds don't produce output for a long time).
|
|
|
|
| |
This avoids wasteful CPU consumption, as reported in bug #432024.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
Trigger the --complete-graph behavior if USE or IUSE will change for
an installed package. This option is enabled by default. This will fix
bug #425558.
|
| |
|
| |
|
|
|
|
| |
This caused the backtracker to bail out too early sometimes.
|
|
|
|
|
| |
We have to distinguish this from the "version" conflict, in order to
avoid invalid vercmp calls when there's not version.
|
|
|
|
|
| |
This will fix a case like that reported in bug #403895, triggered when
the --load-average option is used.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|