| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
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 #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 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 was suggested in the "Don't require assignment of empty variables
in ebuilds?" thread on the gentoo-dev mailing list:
http://thread.gmane.org/gmane.linux.gentoo.devel/78806
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This behaviour is enabled by FEATURES="compress-index". The
resulting file is 'Packages.gz' and its modification time will
match that of 'Packages'.
Web-servers use that copy to avoid repeated on-the-fly compression.
In order to re-use 'atomic_ofstream' usage of 'codecs.zlib_codec'
has been considered and discarded, because 'GzipFile' yields
smaller files. (According to Mark's tests 62% smaller.)
Example usage, Nginx:
location =/Packages {
gzip_static on;
default_type text/plain;
}
Apache httpd (use with caution):
RewriteRule ^(.*)/Packages$ $1/Packages.gz [T=text/plain,E=GZIP:gzip,L]
<FilesMatch "Packages\.gz$">
Header set Content-Encoding gzip
</FilesMatch>
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
This broke in commit e06cb6d66db37ac7ab77acf65038b1f770c13c96 since
CompressedResponseProcessor did not include password auth support.
BUG: The if_modified_since parameter appears to be ignored when using
http password authentication.
|
|
|
|
|
|
|
|
|
|
|
|
| |
This enables Portage to reliably query for remote indices with
HTTP-header If-Modified-Since.
Without this patch mtime is greater than TIMESTAMP for large
indices and slow storages - because writing a large file takes
time. If the difference spans a second (TIMESTAMP 08:00:00, mtime
08:00:01), then Portage will always fetch the remote index because
it will appear being modified (mtime is used there) after the copy
has been made (local copy's TIMESTAMP is used here).
|
| |
|
|
|
|
| |
the local copy is recent enough.
|