public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Brian Harring <ferringb@gmail.com>
To: gentoo-dev@lists.gentoo.org
Cc: wired@gentoo.org
Subject: [gentoo-dev] Re: [gentoo-council] Upcoming Council meeting on July 26th, 1900 UTC
Date: Sat, 17 Jul 2010 16:33:26 -0700	[thread overview]
Message-ID: <20100717233326.GA28010@hrair> (raw)
In-Reply-To: <20100717220501.GA18099@linuxized.com>

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

On Sun, Jul 18, 2010 at 01:05:02AM +0300, Alex Alexander wrote:
> The Council will have its next meeting on the 26th of July, 2010.
> 
> The meeting will begin at 1900 UTC.
> 
> You may use [0] to find out the correct time in your timezone.
> 
> Here's a draft list of the meeting topics so far:
> * vote on adding --as-needed to the default profile's LDFLAGS
> * discuss (and maybe vote on) required-use
>         http://dev.gentoo.org/~ferringb/required-use.html

Adding eclass removal policy to the agenda; it directly affects devs, 
and the previous policy (imo) is misinterpretted slightly.

Specifically, 06/01/08, portage 2.1.4.4 went stable; this had env 
saving/restoration support.  The original council decree was that 
eclasses had to sit for 2 years- I very strongly posit that the time 
period there should've been bound to portage env capabilities rather 
than eclass timelines.

Reasoning is simple enough- w/ a proper PM, eclasses can be 
removed/modified at will without affecting binpkgs/installed pkgs.

So the question I'd like on the agenda is basically if there is any 
reason to preserve the decree- if not, punt it.

~harring

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

       reply	other threads:[~2010-07-17 23:34 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20100717220501.GA18099@linuxized.com>
2010-07-17 23:33 ` Brian Harring [this message]
2010-07-18  3:13   ` [gentoo-dev] Re: [gentoo-council] Upcoming Council meeting on July 26th, 1900 UTC Jorge Manuel B. S. Vicetto
2010-07-18  3:21     ` Theo Chatzimichos
2010-07-18  3:43       ` Brian Harring
2010-07-18  6:06     ` [gentoo-dev] " Christian Faulhammer
2010-07-18 14:03       ` Theo Chatzimichos
2010-07-18 14:21         ` Christian Faulhammer
2010-07-18 15:33           ` Petteri Räty
2010-07-18 17:43             ` Dale
2010-07-18 23:27               ` Duncan
2010-07-19  0:53                 ` Piotr Jaroszyński
2010-07-19  1:11                   ` Dale
2010-07-19  1:12                 ` Dale

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=20100717233326.GA28010@hrair \
    --to=ferringb@gmail.com \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=wired@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