| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
positional and keyword parameters into the super constructor.
svn path=/main/trunk/; revision=5368
|
|
|
|
| |
svn path=/main/trunk/; revision=5357
|
|
|
|
|
|
| |
information to construct one itself.
svn path=/main/trunk/; revision=5356
|
|
|
|
|
|
| |
metadata_overlay together with a volatile in-memory cache module in order to implement cache writes. This allows, for example, a user who's not in the portage group to run `ebuild foo.ebuild digest` (issue reported by Charlie Shepherd <masterdriverz@gentoo.org>).
svn path=/main/trunk/; revision=5354
|
|
|
|
| |
svn path=/main/trunk/; revision=5338
|
|
|
|
|
|
| |
classes since python handles the "in" operator more efficiently than a has_key method call.
svn path=/main/trunk/; revision=4821
|
|
|
|
|
|
| |
with python 2.6.
svn path=/main/trunk/; revision=4470
|
|
|
|
|
|
| |
as suggested by Brian Harring.
svn path=/main/trunk/; revision=3547
|
|
|
|
| |
svn path=/main/trunk/; revision=3546
|
|
|
|
|
|
| |
they've been discarded, leading to regen on each access (only in cases where the user has altered an ebuild in the $PORTDIR).
svn path=/main/trunk/; revision=3544
|
|
readonly cache.
svn path=/main/trunk/; revision=2792
|