public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Jonas Stein <jstein@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Is there any way I can help with pull requests?
Date: Sun, 14 Oct 2018 11:27:16 +0200	[thread overview]
Message-ID: <e3947beb-a5dd-3d9a-f0ad-9c46ed8d4e7a@gentoo.org> (raw)
In-Reply-To: <CAG6MAzSXB=T=xpJL6EGwSb8RzZrp7wyd0wjcHQm30iKmRvZw9g@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1716 bytes --]

On 13/10/2018 15.31, Tomas Mozes wrote:
> You can review the PRs and try to remove common errors before the devs
> check it. Then they don't have to correct the same mistakes again. I don't
> mean you do the corrections, you just suggest them to the PR authors so
> they probably won't repeat them again.
> 
> Common stuff like:
> - using latest eapi (at least for new pkgs)?
> - correct distfile name?
> - proxy maint project in metadata?
> - correct, sorted deps?
> - slot operators for rebuilds?
> - working tests if possible?
> - patches from reliable sources?
> - using || die after commands?
> - reusing eclasseses instead of custom solutions?
> - openrc/systemd done right?
> - is it secure?
> - you name it... :)
> 
> Maybe we could script some of these to help too.
> 

This is my list of most frequent comments on new ebuilds:

* Please test the ebuild with repoman full -d -x
https://wiki.gentoo.org/wiki/Repoman
* We always try to use the latest EAPI, please bump to EAPI=7
* Please remove obsolete lines
* KEYWORDS need ~ after a version bump run ekeyword ~all YOUREBUILD
* please fix the header. (see /usr/portage/skel.ebuild and
https://devmanual.gentoo.org/ebuild-writing/eapi/)
* We usually sort the KEYWORDS as ekeywords does. This makes comparison
between packages easier. Simply run ekeywords on the ebuild to let it sort.
* Please be more specific in the DESCRIPTION. The objective description
may be <=80 characters long.
* Please introduce local variables with "local"
* A bot can look for additional mistakes, if you upload a PR via github


You could create a checklist on the wiki.
Some of these tests can be done by repoman

-- 
Best,
Jonas


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 636 bytes --]

  reply	other threads:[~2018-10-14  9:27 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-13 11:28 [gentoo-dev] Is there any way I can help with pull requests? Ralph Seichter
2018-10-13 12:57 ` Thomas Deutschmann
2018-10-13 13:33   ` Ralph Seichter
2018-10-13 16:37   ` Ralph Seichter
2018-10-13 12:59 ` James Le Cuirot
2018-10-13 18:20   ` Rich Freeman
2018-10-13 18:32   ` Mikle Kolyada
2018-10-20  0:33     ` Michael Orlitzky
2018-10-20  8:05       ` Mikle Kolyada
2018-10-20 15:02         ` Michael Orlitzky
2018-10-13 13:11 ` Corentin “Nado” Pazdera
2018-10-14 18:17   ` Andreas K. Huettel
2018-10-15  8:30   ` Corentin “Nado” Pazdera
2018-10-13 13:31 ` Tomas Mozes
2018-10-14  9:27   ` Jonas Stein [this message]
2018-10-13 18:00 ` Michał Górny
2018-10-13 18:18   ` Ralph Seichter
2018-10-16 18:25     ` Virgil Dupras
2018-10-16 18:36       ` Bernd Waibel
2018-10-16 19:14       ` Ralph Seichter
2018-10-16 20:15         ` Rich Freeman

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=e3947beb-a5dd-3d9a-f0ad-9c46ed8d4e7a@gentoo.org \
    --to=jstein@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