From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev <gentoo-dev@lists.gentoo.org>
Subject: [gentoo-dev] [RFC] Allowing pkgcheck as a replacement for repoman
Date: Mon, 09 Sep 2019 08:23:59 +0200 [thread overview]
Message-ID: <5c96ec43b596a283da4e01cd241cfe412cbef589.camel@gentoo.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2003 bytes --]
Hi,
This is something I'd like to pass to the Council for the next meeting.
TL;DR: I'd like to allow using pkgcheck instead of repoman because it's
5-26 times faster and more convenient to use.
The current policy requires you to test your packages with repoman prior
to committing. However, repoman is both pretty inconvenient, unreadable
and slow. For example, for the cleanup of old versions in 4 packages I
have staged right now:
$ time sh -c '(for x in $(git diff --name-only origin | cut -d/ -f1-2 | uniq); do ( cd $x && repoman full -d ); done)'
RepoMan scours the neighborhood...
RepoMan sez: "If everyone were like you, I'd be out of business!"
RepoMan scours the neighborhood...
RepoMan sez: "If everyone were like you, I'd be out of business!"
RepoMan scours the neighborhood...
repo.eapi-deprecated 1
media-libs/stops/stops-0.3.0-r1.ebuild: 5
RepoMan sez: "You're only giving me a partial QA payment?
I'll take it this time, but I'm not happy."
RepoMan scours the neighborhood...
RepoMan sez: "If everyone were like you, I'd be out of business!"
real 1m46,236s
user 1m38,524s
sys 0m7,818s
For comparison, pkgcheck:
$ time pkgcheck scan --git-disable $(git diff origin --name-only | cut -d/ -f1-2 | sort -u)
media-libs/stops
DeprecatedEAPI: version 0.3.0-r1: uses deprecated EAPI 5
real 0m4,408s
user 0m3,985s
sys 0m0,559s
Note that this is with warm profile cache. Without it:
$ time pkgcheck scan --profile-cache false --git-disable $(git diff origin --name-only | cut -d/ -f1-2 | sort -u)
media-libs/stops
DeprecatedEAPI: version 0.3.0-r1: uses deprecated EAPI 5
real 0m18,791s
user 0m16,279s
sys 0m0,611s
PkgCheck implements most of the checks currently in repoman,
and implements some more (e.g. for bad SRC_URI filenames). It finally
had new releases recently, and I think it's matured enough for basic
development work.
WDYT?
--
Best regards,
Michał Górny
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 618 bytes --]
next reply other threads:[~2019-09-09 6:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-09 6:23 Michał Górny [this message]
2019-09-09 15:38 ` [gentoo-dev] [RFC] Allowing pkgcheck as a replacement for repoman Alec Warner
2019-09-09 15:44 ` Michał Górny
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5c96ec43b596a283da4e01cd241cfe412cbef589.camel@gentoo.org \
--to=mgorny@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox