From: Michael 'veremitz' Everitt <gentoo@veremit.xyz>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [Policy change] Package masking of live ebuilds
Date: Tue, 18 Feb 2020 23:19:31 +0000 [thread overview]
Message-ID: <c3bacaae-53f6-11d1-baa8-44bd6783dd9f@veremit.xyz> (raw)
In-Reply-To: <uv9o3k6zo@kph.uni-mainz.de>
[-- Attachment #1.1: Type: text/plain, Size: 860 bytes --]
On 18/02/20 19:52, Ulrich Mueller wrote:
> The devmanual says about live ebuilds:
>
> | CVS ebuilds must be either with empty KEYWORDS or package.masked
> | (but not both). Empty KEYWORDS are strongly preferred. This applies
> | to "live" ebuilds (-9999) and to ebuilds that extract a static
> | revision but still use CVS for fetching.
>
> As of today, I count 2123 live ebuilds in the Gentoo repository with
> empty KEYWORDS and 1 (one) ebuild with non-empty KEYWORDS but
> package.masked.
>
> So, can we finally make empty KEYWORDS mandatory and drop the part
> about package.masking?
>
> Ulrich
>
> [1] https://devmanual.gentoo.org/ebuild-writing/functions/src_unpack/cvs-sources/index.html
> (Yes, there really should be a chapter about Git sources ...)
This sounds like an ideal opportunity for repoman/pkgcheck warnings .. no?
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
prev parent reply other threads:[~2020-02-18 23:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-18 19:52 [gentoo-dev] [Policy change] Package masking of live ebuilds Ulrich Mueller
2020-02-18 21:49 ` William Hubbs
2020-02-18 23:19 ` Michael 'veremitz' Everitt [this message]
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=c3bacaae-53f6-11d1-baa8-44bd6783dd9f@veremit.xyz \
--to=gentoo@veremit.xyz \
--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