Gentoo Archives: gentoo-dev

From: Alec Warner <antarus@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in app-crypt/gpa: gpa-0.9.3.ebuild ChangeLog gpa-0.9.1_pre20100416-r1.ebuild
Date: Tue, 28 Aug 2012 13:57:41
Message-Id: CAAr7Pr_ZEyH=D+3GaHm+KTaef+LDDb7uSa--S1pNH0jvY71KiQ@mail.gmail.com
In Reply to: Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in app-crypt/gpa: gpa-0.9.3.ebuild ChangeLog gpa-0.9.1_pre20100416-r1.ebuild by Rich Freeman
1 On Tue, Aug 28, 2012 at 4:25 AM, Rich Freeman <rich0@g.o> wrote:
2 > On Mon, Aug 27, 2012 at 10:05 PM, Duncan <1i5t5.duncan@×××.net> wrote:
3 >> That's all I'm saying. It's being made a whole lot less pleasant that it
4 >> might be... for what reason? Just to satisfy someone's ego that they're
5 >> right and can /force/ compliance? Yuck!
6 >
7 > Honestly, while I might agree with that sentiment on some of these
8 > threads, my only complaint with Ciaran's original response was that he
9 > could have been a bit more direct with his concern. Rather than
10 > stating that EXTRA_* does not exist as far as ebuilds go, he could
11 > have just stated that PMS does not allow these variables to be used by
12 > an ebuild.
13 >
14 > However, the reply to that email makes it clear that even though it
15 > was unstated Ciaran's meaning was understood.
16 >
17 > Sure, he didn't get into the why, but I'm not sure I'd expect that.
18 > I'd probably state it, but I'm probably the second-most-verbose person
19 > on this list. :)
20 >
21 > If somebody filed a bug against my package and pointed out that
22 > something was illegal per PMS, probably the first thing I'd do is read
23 > it to fully understand the situation, and then if I had a concern I'd
24 > probably ask via irc/private email/etc. That is as much to avoid
25 > making a fool out of myself in public, but also because when somebody
26 > who is obviously knowledgeable points out something they consider a
27 > flaw, it isn't a bad idea to give their concern full consideration.
28 >
29 > Sure, if PMS is wrong it ought to be fixed, but the whole point of
30 > having specifications is that you don't toss them the moment you don't
31 > like what they say. Then again, I work on regulated software in my
32 > real job, and even if the spec is wrong changing it still involves a
33 > process - you don't just ignore it (any behavior in violation of the
34 > spec is an automatic bug - even if the bug is to fix the spec - and
35 > unless pretty trivial is justification to prevent release (often this
36 > is done anyway since it is usually less work to just fix the problem
37 > than justify to the world not doing it)).
38
39 I'm not sure if you have noticed, but many developers in Gentoo
40 dislike process ;)
41
42 >
43 > In any case, it is best to not take these sorts of things personally
44 > all around. Most of us are here because our perverse tastes consider
45 > this stuff fun! :) Might as well keep it that way...
46 >
47 > Rich
48 >

Replies