| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
| |
This will fix bug #332217.
|
|
|
|
| |
Now is won't force metadata-transfer unless it's absolutely necessary.
|
| |
|
| |
|
|
|
|
|
| |
If there is an existing metadata/md5-cache directory, then it's not
necessary to forcibly enable metadata-transfer.
|
|
|
|
|
|
|
| |
Auto-detect cache-formats from the corresponding directories when
cache-formats is not specifed in layout.conf, and prefer md5-dict if
available. After this behavior is deployed in stable portage, the
default egencache format can be changed to md5-dict.
|
| |
|
|
|
|
|
| |
Similar code was added to getUseMask in commit
af50fee789e71c1fff0b405db4cf55b618b73466.
|
|
|
|
| |
package.use.stable.force and package.use.stable.mask in EAPI >=5.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Use grabdict so the values are stored as lists like writedict expects.
|
| |
|
|
|
|
|
| |
This will avoid a potential syntax error in save-ebuild-env.sh if a
saved environment containing corrupt EAPI is sourced.
|
| |
|
| |
|
|
|
|
|
| |
This is especially necessary when running in prefix mode, since
sys.path may contain the path for a different version of portage.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Allow sets of packages installed before or after a specific date.
The date may be specified explicitly (in dateformat which defaults to "%x %X")
or seconds since Epoch, or implicitly as an installation date or a filestamp.
For example, the following sets can be specified in /etc/portage/sets.conf:
[date1]
class = portage.sets.dbapi.DateSet
mode = older
date = 08/31/12 10:00:00
dateformat = %%x %%X
[date2]
class = portage.sets.dbapi.DateSet
mode = newer
seconds = 1346400000
[date3]
class = portage.sets.dbapi.DateSet
package = sys-devel/gcc:4.7
[date4]
class = portage.sets.dbapi.DateSet
filestamp = /usr/bin/gcc
|
| |
|
| |
|
|
|
|
| |
See <https://bugs.freedesktop.org/show_bug.cgi?id=35844#c6>.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
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
|