Complain only about deprecated eclasses that are inherited directly.
Checking indirectly inherited eclasses is pointless since the ebuild
maintainer can't really do anything about it --- it is up to
the maintainer of one of the directly inherited eclasses.
---
pym/repoman/checks.py | 16
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Friends, here is the meeting summary:
- -We'll merge the fakeroot patches[0].
- -Trofi's repoman patch is mostly OK as far as Michał and I are
concerned. I will respond to his thread on the ML. Tom or whoever's
doing repoman now needs to ACK it.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 25/07/14 00:11, Sergei Trofimovich wrote:
- assert(h.known_maintainer('sping'))
- assert(h.known_maintainer('sp...@gentoo.org'))
+ assert(h.known_maintainer('slyfox'))
+ assert(h.known_maintainer('sly...@gentoo.org'))
Add checks for common mistakes when installing bash completion files:
legacy directory, incorrect naming, missing aliases, deprecated 'have'
function.
Changes in v2:
- silenced output (error) when sourcing completion files,
- faked _have() to enable all conditional completions in the tested
Attached is an updated patch which adds logic to account for the fact
that depth is meaningless for packages that are not reachable as deep
dependencies of arguments. I'm fairly confident that everything is
accounted for now, so I do not anticipate any more updates to this patch
unless somebody
Most of you know about the plugin-sync branch of our portage.git repo.
I believe it is ready for review and merge into master to become the
new sync code for the future.
Rather than follow this with 49 patch mails ... I produced a final git
diff of all the changes. I have cleaned up and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Wed, 03 Sep 2014 14:02:13 +0200
Alexander Berntsen berna...@gentoo.org wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Friends, here is the meeting summary:
- -We'll merge the fakeroot patches[0].
- -Trofi's repoman patch is
On Wed, 3 Sep 2014 17:35:40 -0700
Brian Dolbec dol...@gentoo.org wrote:
Most of you know about the plugin-sync branch of our portage.git repo.
I believe it is ready for review and merge into master to become the
new sync code for the future.
Rather than follow this with 49 patch mails ...
