| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
|
|
| |
This helps to prevent inappropriate use of the sed wrapper on GNU
systems, which commonly occurs when users install portage manually
during recovery situations.
|
| |
|
|
|
|
|
| |
Instead, just use conditionals where appropriate inside
bin/ebuild-helpers/* scripts.
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
o s/uses_root/uses_eroot/g -- This name was chosen
before its meaning was changed; update it to reflect its purporse.
o Fix a left-over "<root>" arg-doc that never got updated to "<eroot>"
o If a provided eroot argument was shorter than the ${EPREFIX}, portageq
was truncating it down to nothing and activating relative root,
which means this became equivalent to an explicit argument of
"${PWD}/${EPREFIX}/". This is obviously wrong; and a simple case
of failing to sanity-check inputs from an interface that changed in a
backward-incompatible way.
There's no provision in portageq to query EROOT's that don't end in
${EPREFIX}; so if the user makes such a request, instead of doing
something pathological, dump a helpful error message and bail with
a nonzero exit code.
Signed-off-by: Gregory M. Turner <gmturner007@ameritech.net>
|
|
|
|
| |
See bug #21310.
|
| |
|
| |
|
|
|
|
| |
See bug #382963.
|
|
|
|
|
| |
See bug #401239 and the PMS patch:
http://git.overlays.gentoo.org/gitweb/?p=proj/pms.git;a=commit;h=25fb5fca6674215ea8aaa3d0ec3dd3df451eec07
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
| |
See bug #379497 and the PMS patch:
http://git.overlays.gentoo.org/gitweb/?p=proj/pms.git;a=commit;h=b7750e67b4772c1064543defb7df6a556f09807b
|
|
|
|
|
|
|
| |
A real apply_user_patches implementation will be a bit more work, so
for now we'll just implement the minimum amount necessary to satisfy
the spec:
http://git.overlays.gentoo.org/gitweb/?p=proj/pms.git;a=commit;h=a8bf7862967cce36b7f1b408934a774126da2538
|
| |
|
|
|
|
|
| |
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 #363005 and the PMS patch:
http://git.overlays.gentoo.org/gitweb/?p=proj/pms.git;a=commit;h=3ec4b3c22582a8ec206bce1e93bab377d7b264b5
|
|
|
|
|
| |
See bug #390765 and the PMS patch:
http://git.overlays.gentoo.org/gitweb/?p=proj/pms.git;a=commit;h=76ddca560da42fd968c53a2a0c38a6ac840a7ad4
|
| |
|
|
|
|
|
| |
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 fix bug #432862.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
This will be needed in order to support stable use.mask/force for
bug #431078.
|
|
|
|
| |
This will fix bug #421099.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
This fixes AttributeError exceptions for API consumers that override
sys.std* streams pseudo-file objects.
|
| |
|
|
|
|
| |
This will fix bug #432024.
|
|
|
|
|
| |
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.
|
|
|
|
| |
This will fix bug #392565.
|
|
|
|
| |
FEATURES=webrsync-gpg forces it to recompress in the foreground.
|