This adds an egencache --update-pkg-desc-index action which generates
a plain-text index of package names, versions, and descriptions. The
index can then be used to optimize emerge --search / --searchdesc
actions.
X-Gentoo-Bug: 525718
X-Gentoo-Bug-URL:
On 11/03/2014 09:42 PM, Zac Medico wrote:
This updated patch causes indexed search to be enabled only for
searchdesc, since indexed variants can actually be slower when
only package names need to be searched.
With the recent pkg_desc_index_line_read optimization (removal of
package name and
On 11/03/2014 01:42 PM, Brian Dolbec wrote:
I know the above times are probably slowed by not having overlays indexed,
but it is still a significant speedup.
esearch is only marginally slower doing a -S search than a regular pkg-name
search, typically just over 0.2 seconds
The above was
The IndexedPortdb class uses pkg_desc_index to optimize searchs for
package names and descriptions. If the package description index is
missing from a particular repository, then all metadata for that
repository is obtained using the normal pordbapi.aux_get method.
This class only implements a
The new emerge --search-index option, which is enabled by default,
causes pkg_desc_index to be used for search optimization. The search
index needs to be regenerated by egencache after changes are made to
a repository (see the --update-pkg-desc-index action).
For users that would like to modify
The doebuild function has a boolean unpacked variable which it sets
to True if it determines that the unpack phase has already executed
and the last modification times of the distfiles are older than the
last modification time of WORKDIR. The code which sets the unpacked
flag does not need to run
In ebuild.sh, $T/environment is loaded for most phases, but it should
always start with a fresh environment for pkg_setup. Therefore, skip
environment loading for pkg_setup.
X-Gentoo-Bug: 528274
X-Gentoo-Bug-URL: https://bugs.gentoo.org/show_bug.cgi?id=528274
---
bin/ebuild.sh | 2 +-
1 file
In ebuild.sh, $T/environment is loaded for most phases, but it should
always start with a fresh environment for pkg_setup. Therefore, skip
environment loading for pkg_setup.
This also requires a change in the config.environ method, in order
to ensure that the calling environment is inherited by
