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: [gentoo-project] Re: Call for agenda items - Council meeting 2013-04-09
Date: Tue, 9 Apr 2013 13:12:33 -0500	[thread overview]
Message-ID: <20130409181233.GA10952@comet.hsd1.mn.comcast.net> (raw)
In-Reply-To: <20130408232028.56cdad67@caribou.gateway.2wire.net>

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

On 23:20 Mon 08 Apr     , Ryan Hill wrote:
> Hrm.  I just meant that package eclasses suck. I hate the fact that they
> effectively make stable moot.  There is no such thing as a stable keyword for a
> package built by an eclass.  It's like working without a net.  When it's a core
> system package it's twice as bad.
> 
> As far as these eclasses go, toolchain is the worst.  Yes, it is fragile
> and complex.  It's over a decade's worth of spaghetti code.  It builds 12 years
> of gcc releases.  It's hairy.  Everything depends on everything else, and
> everything is based on assumptions and implications that may or may not still
> be relevant.  Making "obviously" correct changes has often broken something
> somewhere else, time and again.  I'm not telling you this for some kind of
> perverse bragging rights.  It's not something to be proud of.  I just want you
> to understand how easy it is to fuck things up.
> 
> When it breaks, it breaks stable.  I absolutely hate breaking stable.  I lose
> sleep over it.

You could probably deal with this through much more aggressive bumping 
of eclass versions in concert with ebuild bumps, followed by eclass 
freezes once their users go stable.

-- 
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: 198 bytes --]

  parent reply	other threads:[~2013-04-09 18:12 UTC|newest]

Thread overview: 66+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-26 17:14 [gentoo-project] Call for agenda items - Council meeting 2013-04-09 Ulrich Mueller
2013-03-30 10:22 ` Michał Górny
2013-03-30 11:51   ` Ulrich Mueller
2013-04-02 14:25 ` [gentoo-project] " Ulrich Mueller
2013-04-02 15:25   ` Rich Freeman
2013-04-02 15:31   ` Markos Chandras
2013-04-02 16:42     ` Michał Górny
2013-04-03  9:07     ` Ralph Sennhauser
2013-04-03  9:31       ` vivo75
2013-04-03 15:22         ` Zac Medico
2013-04-03 18:11           ` vivo75
2013-04-05 16:54       ` Ulrich Mueller
2013-04-06 21:43         ` Ryan Hill
2013-04-06 21:50           ` Pacho Ramos
2013-04-06 22:37           ` Andreas K. Huettel
2013-04-07  2:05             ` Ryan Hill
2013-04-07  7:27               ` Ciaran McCreesh
2013-04-07  9:34                 ` Ryan Hill
2013-04-07 14:00                   ` Tom Wijsman
2013-04-07 14:46                     ` Rich Freeman
2013-04-07 14:47                       ` Ciaran McCreesh
2013-04-07 15:07                       ` Tom Wijsman
2013-04-07 10:13                 ` Markos Chandras
2013-04-07 10:41                   ` Ben de Groot
2013-04-07 10:51                     ` Markos Chandras
2013-04-07 14:23                       ` Tom Wijsman
2013-04-07 11:05                   ` Michał Górny
2013-04-07 15:06                   ` Michael Palimaka
2013-04-07 11:13               ` Andreas K. Huettel
2013-04-07 12:08               ` Andreas K. Huettel
2013-04-07 12:24                 ` Rich Freeman
2013-04-07 13:37                   ` Andreas K. Huettel
2013-04-07 13:43                     ` Rich Freeman
2013-04-07 14:13                       ` Tom Wijsman
2013-04-07 14:36                   ` Ciaran McCreesh
2013-04-09  5:20                 ` Ryan Hill
2013-04-09  5:57                   ` Michał Górny
2013-04-09  8:13                     ` Rich Freeman
2013-04-09 19:24                     ` Mike Frysinger
2013-04-09 20:24                       ` Michał Górny
2013-04-09 20:57                         ` Mike Frysinger
2013-04-10  0:07                         ` Ryan Hill
2013-04-10  3:41                           ` Michał Górny
2013-04-10 13:02                             ` vivo75
2013-04-10 13:25                               ` Tom Wijsman
2013-04-09 18:12                   ` Donnie Berkholz [this message]
2013-04-10 12:20                     ` hasufell
2013-04-10 13:00                       ` Tom Wijsman
2013-04-10 13:16                         ` hasufell
2013-04-10 13:40                           ` Tom Wijsman
2013-04-10 14:20                             ` hasufell
2013-04-10 15:02                               ` Tom Wijsman
2013-04-10 16:43                                 ` Ian Stakenvicius
2013-04-10 17:12                                   ` Tom Wijsman
2013-04-10 19:30                     ` Mike Frysinger
2013-04-10 20:22                       ` Rich Freeman
2013-04-11  3:53                         ` Ryan Hill
2013-04-07 13:58               ` Tom Wijsman
2013-04-02 22:37   ` "Paweł Hajdan, Jr."
2013-04-03  5:02     ` Zac Medico
2013-04-03  9:56   ` Thomas Sachau
2013-04-03  9:54     ` Ciaran McCreesh
2013-04-03 19:06       ` Thomas Sachau
2013-04-04  5:38         ` Ciaran McCreesh
2013-04-03 10:14   ` Michał Górny
2013-04-02 22:13 ` [gentoo-project] Council meeting: Tuesday 9 April 2013, *** 19:00 UTC *** Ulrich Mueller

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=20130409181233.GA10952@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