From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev-announce <gentoo-dev-announce@lists.gentoo.org>
Cc: gentoo-dev <gentoo-dev@lists.gentoo.org>
Subject: [gentoo-dev-announce] New QA policy: ebuild code must be wholly contained within PMS-defined files
Date: Fri, 24 Mar 2017 16:50:01 +0100 [thread overview]
Message-ID: <1490370601.1319.4.camel@gentoo.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 757 bytes --]
Hi, everyone.
On behalf of the QA team, I would like to shortly announce that the QA
team has unanimously approved the following policy:
===
The ebuild code must be wholly contained in files that are defined by
the PMS, which as of 2017-03-24 are .ebuild and .eclass files. It is
explicitly forbidden to split the ebuild code into additional files that
are loaded via source, eval or any other possible method.
===
Furthermore, with 7:4 votes, the QA team members have decided that
the policy applies both to new and existing ebuilds. The known
violations are planned to be fixed today as part of the (independent)
effort on fixing PMS violations.
Rationale + vote: https://bugs.gentoo.org/612630
--
Best regards,
Michał Górny
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 963 bytes --]
reply other threads:[~2017-03-24 17:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1490370601.1319.4.camel@gentoo.org \
--to=mgorny@gentoo.org \
--cc=gentoo-dev-announce@lists.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