public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: William Hubbs <williamh@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Call for agenda items - Council meeting 2013-10-08
Date: Sat, 2 Nov 2013 13:52:17 -0500	[thread overview]
Message-ID: <20131102185217.GA32534@linux1> (raw)
In-Reply-To: <201309242248.36395.dilfridge@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 974 bytes --]

Council members,

a policy was just pointed out to me on IRC today that I think we should
look at changing with regard to how we are supposed to deal with live
ebuilds.

According to the dev manual, all live ebuilds are supposed to be put in
package.mask [1]. The reality of the situation, however, is that we are
mostly using empty keywords for live ebuilds.

I think the policy of requiring package.mask for live ebuilds happened
before the empty keywords option was available.

Can we discuss and maybe vote on how we want live ebuilds in the tree? I
see three possibilities:

1) empty keywords (this appears to be what most people are doing)
2) package.mask (not required, the way I see it, because of 1 and
because package.mask shouldn't be permanent)
3) both package.mask and empty keywords (this would be double masking,
and again shouldn't be necessary)

Thoughts?

William

[1]
http://devmanual.gentoo.org/ebuild-writing/functions/src_unpack/cvs-sources/index.html

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  parent reply	other threads:[~2013-11-02 18:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-24 20:48 [gentoo-project] Call for agenda items - Council meeting 2013-10-08 Andreas K. Huettel
2013-09-25 20:22 ` Markos Chandras
2013-11-02 18:52 ` William Hubbs [this message]
2013-11-02 19:03   ` Agostino Sarubbo
2013-11-02 19:25   ` Rick "Zero_Chaos" Farina
2013-11-04  0:37     ` [gentoo-project] " Jonathan Callen
2013-11-02 21:24   ` [gentoo-project] " William Hubbs
2013-11-02 23:50     ` Markos Chandras

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=20131102185217.GA32534@linux1 \
    --to=williamh@gentoo.org \
    --cc=gentoo-project@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