public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: Donnie Berkholz <dberkholz@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: Re: [gentoo-project] Call for agenda items - Council meeting 2014-02-25
Date: Thu, 20 Feb 2014 21:28:15 -0600	[thread overview]
Message-ID: <20140221032815.GE8819@comet.hsd1.mn.comcast.net> (raw)
In-Reply-To: <1717049.ym98kJ4Tps@kailua>

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

On 12:41 Thu 13 Feb     , Andreas K. Huettel wrote:
> > On Tue, Feb 11, 2014 at 08:46:33PM +0100, Andreas K. Huettel wrote:
> > > Stable keywords on "~arch only" architectures in ebuilds.
> > > 
> > > Possible options include
> > > * drop 'em all
> > > * require a "dropping by tree aging"
> > > * allow for arch-team purposes limited stable marking, but package
> > > maintainers neednt care
> > 
> > How about moving the status of ~arch only profiles to exp in
> > profiles.desc as vapier suggested, or is that covered in your last
> > option?
> 
> Can do that, sure... I didnt really intend to exhaustively describe everything 
> when writing this mail, that's why I linked to bug and ml thread.

Yeah, this idea of dropping keywords wholesale totally screws with new 
or revived ports. I much prefer repoman ignoring stable on a given arch 
by marking it exp (during active porting) or dev (when the port is 
thought to basically work) as Mike described in 
<https://bugs.gentoo.org/show_bug.cgi?id=498332#c5> / 
<https://bugs.gentoo.org/show_bug.cgi?id=498332#c11>.

-- 
Thanks,
Donnie

Donnie Berkholz
Council Member / Sr. Developer, Gentoo Linux <http://dberkholz.com>
Analyst, RedMonk <http://redmonk.com/dberkholz/>

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

  reply	other threads:[~2014-02-21  3:28 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-10 14:45 [gentoo-project] Call for agenda items - Council meeting 2014-02-25 Andreas K. Huettel
2014-02-10 15:39 ` Ulrich Mueller
2014-02-10 16:00   ` Andreas K. Huettel
2014-02-10 16:22     ` Ruud Koolen
2014-02-10 18:03       ` Tom Wijsman
2014-02-10 18:49         ` Ciaran McCreesh
2014-02-10 18:51         ` Ulrich Mueller
2014-02-10 19:07 ` hasufell
2014-02-11  2:39   ` Rick "Zero_Chaos" Farina
2014-02-11 23:20     ` hasufell
2014-02-20  9:33   ` Ulrich Mueller
2014-02-20 15:46     ` hasufell
2014-02-11 19:46 ` Andreas K. Huettel
2014-02-13  4:35   ` William Hubbs
2014-02-13 11:41     ` Andreas K. Huettel
2014-02-21  3:28       ` Donnie Berkholz [this message]
2014-02-21  0:14 ` Chí-Thanh Christopher Nguyễn
2014-02-21  3:47   ` Donnie Berkholz
2014-02-21  4:03     ` Rich Freeman
2014-02-21  4:04       ` Donnie Berkholz
2014-02-21 13:32         ` Anthony G. Basile
2014-02-21  8:38     ` Michał Górny
2014-02-21 10:34       ` Tom Wijsman
2014-02-24 16:46     ` Chí-Thanh Christopher Nguyễn
2014-02-24 18:59       ` Tom Wijsman
2014-02-24 21:43         ` Chí-Thanh Christopher Nguyễn
2014-02-24 23:55           ` Tom Wijsman
2014-02-25  0:12           ` Rich Freeman
2014-02-24 23:13       ` Patrick Lauer
2014-02-24 23:54 ` Patrick Lauer

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=20140221032815.GE8819@comet.hsd1.mn.comcast.net \
    --to=dberkholz@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