From: Donnie Berkholz <dberkholz@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] new `usex` helper
Date: Thu, 22 Sep 2011 19:41:29 -0500 [thread overview]
Message-ID: <20110923004129.GA3589@comet> (raw)
In-Reply-To: <CAAr7Pr-Quf2pNOrsNDcnnj3Avp92ggw1=Hxio7uhdcGONxSkdg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1535 bytes --]
On 09:37 Wed 21 Sep , Alec Warner wrote:
> On Wed, Sep 21, 2011 at 6:11 AM, Donnie Berkholz <dberkholz@gentoo.org> wrote:
> > Not really, because when you update a bundled lib you actually make
> > your whole app compile with it. People change the APIs of eclasses
> > and then just let every internal consumer (ebuilds in gentoo-x86)
> > break. Maybe if we put the burden on the one who changed the API,
> > like the Linux kernel model, it would bother me less.
>
> I think people do this for three reasons.
>
> 1) There are no refactoring tools that I know of for bash.
> 2) There exist some package maintainers that will yell at you if you
> touch their packages for any reason.
To refer to the Linux model again, you send patches to the maintainers,
and they just commit them. This is much less effort than figuring out to
handle some incomprehensible change to an already weird eclass and then
sorting out how to deal with it across 20 or 30 packages.
> 3) Breaking things means they get fixed.
>
> We have this notify -> deprecate -> break workflow; I actually don't
> mind it (but only because I've seen it used elsewhere.)
I do, because I don't have time to deal with other people breaking my
packages, whether they're in gentoo-x86, the science overlay, or my
personal one. I've got more important things to deal with, within Gentoo
and in the rest of my life.
--
Thanks,
Donnie
Donnie Berkholz
Council Member / Sr. Developer
Gentoo Linux
Blog: http://dberkholz.com
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-09-23 0:42 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-13 21:56 [gentoo-dev] new `usex` helper Mike Frysinger
2011-09-13 22:01 ` Alec Warner
2011-09-13 22:13 ` Mike Frysinger
2011-09-13 23:08 ` Brian Harring
2011-09-14 2:45 ` Mike Frysinger
2011-09-14 3:04 ` Brian Harring
2011-09-14 3:43 ` Mike Frysinger
2011-09-14 3:56 ` Brian Harring
2011-09-14 6:02 ` Ulrich Mueller
2011-09-14 14:53 ` Mike Frysinger
2011-09-14 2:02 ` Donnie Berkholz
2011-09-14 2:14 ` Brian Harring
2011-09-14 19:16 ` Donnie Berkholz
2011-09-15 0:29 ` Brian Harring
2011-09-16 3:00 ` Donnie Berkholz
2011-09-16 9:06 ` Brian Harring
2011-09-16 12:30 ` Donnie Berkholz
2011-09-16 14:04 ` Michał Górny
2011-09-16 17:27 ` Alec Warner
2011-09-16 20:43 ` Brian Harring
2011-09-18 3:59 ` Donnie Berkholz
2011-09-18 11:22 ` Brian Harring
2011-09-19 3:16 ` Donnie Berkholz
2011-09-20 21:20 ` Brian Harring
2011-09-21 13:11 ` Donnie Berkholz
2011-09-21 16:37 ` Alec Warner
2011-09-23 0:41 ` Donnie Berkholz [this message]
2011-09-23 1:04 ` Alec Warner
2011-09-23 1:15 ` Donnie Berkholz
2011-09-17 21:37 ` Zac Medico
2011-09-14 2:47 ` Mike Frysinger
2011-09-14 5:34 ` Ciaran McCreesh
2011-09-14 19:23 ` Donnie Berkholz
2011-09-14 15:03 ` Mike Frysinger
2011-09-21 19:25 ` Mike Frysinger
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=20110923004129.GA3589@comet \
--to=dberkholz@gentoo.org \
--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