| 1 |
On Mon, 21 Oct 2013 15:32:10 +0200 |
| 2 |
Jeroen Roovers <jer@g.o> wrote: |
| 3 |
|
| 4 |
> On Sun, 20 Oct 2013 12:41:02 +0100 |
| 5 |
> Markos Chandras <hwoarang@g.o> wrote: |
| 6 |
> |
| 7 |
> > No I never meant broken depgraphs. Well for broken deps, repoman |
| 8 |
> > does not let you commit. If you use --force to workaround broken |
| 9 |
> > deps, well, then you get what you deserve. |
| 10 |
> |
| 11 |
> No, apparently tomwij can get not only away with this (and apparently |
| 12 |
> others as well on a regular basis). Not just that: he gets to write a |
| 13 |
> lengthy "apology" that merely blames others / documentation / common |
| 14 |
> sense, and then proceeds to call me "unprofessional" for pointing out |
| 15 |
> in public the several mistakes he made. I feel very much that he's not |
| 16 |
> getting it (what he deserves). |
| 17 |
|
| 18 |
This is a first time I mask an USE flag on a package for a very small |
| 19 |
single issue, please do not get upset over it. If I do it perfectly on |
| 20 |
other achitectures which do not point anything out about it; then there |
| 21 |
must be a reason as to why this happened *, please assume good faith |
| 22 |
and do not see my explanation as a way to blame people or words. You or |
| 23 |
your comment is not the reason to it, rather my misinterpretation of it. |
| 24 |
|
| 25 |
My replies are rather intended to make sure "apparently others" do not |
| 26 |
experience this again in the future; by introducing consistency, |
| 27 |
deciding on policy, clarifying documentation and so on... |
| 28 |
|
| 29 |
It simply does not work to say to me that "you're supposed to" when |
| 30 |
that doesn't reflect what other arches do as well as the docs; I have |
| 31 |
learned early on to not be convinced by inviduals, but rather to base |
| 32 |
myself on consensus as to avoid people telling me conflicted matters. |
| 33 |
|
| 34 |
To some extent I might be trying to be too professional; but, I'm |
| 35 |
rather scared of not being professional enough, so I try not to be |
| 36 |
careless when checking whether there is a consensus on matters. |
| 37 |
|
| 38 |
You very well know that this is not intended, that I apologize and that |
| 39 |
I will not let it happen again; so, the only thing left I ask from |
| 40 |
Gentoo and you is to bring more consistency in this matter so all of us |
| 41 |
do not have to go through this again. |
| 42 |
|
| 43 |
If there's no consistency, no policy for the HPPA exception and missing |
| 44 |
documentation; then ask yourself, what alerts and/or prevents the next |
| 45 |
new developer from making this mistake again once he gets to USE flag |
| 46 |
dependencies that need to be masked? |
| 47 |
|
| 48 |
Nothing, and that concerns me. |
| 49 |
|
| 50 |
As for blaming you; it is quite the opposite, I have actually been |
| 51 |
trying to become friends with you because we share some common concerns |
| 52 |
(bug wrangling, keeping #gentoo clean, ...) but I find it much harder |
| 53 |
to do that these days running into these roadblocks ("atrocity" when |
| 54 |
making a mistake because of an unexpected comment, changing the patch |
| 55 |
name in tinyproxy, getting away and getting what I deserve, ...) that |
| 56 |
are the result of us not communicating in a professional way. |
| 57 |
|
| 58 |
I very well respect your position as an arch member, your concerns to |
| 59 |
keep maintaining the arch easy and more; I'm not bothered by you, even |
| 60 |
rather admire some of the work you do. |
| 61 |
|
| 62 |
I do speak up to improve our maintenance to be more efficient, to |
| 63 |
improve Gentoo and to increase the general user experience; then if |
| 64 |
problems or complexity sits in the way of that, I want to |
| 65 |
explain, discuss and improve it. When that is reasonably possible. |
| 66 |
|
| 67 |
Please note that I however do not insist on it; if nobody's interested, |
| 68 |
then I am okay with that. What I didn't get here is why that comment is |
| 69 |
in place in the HPPA package.use.mask; my confusion on this should be |
| 70 |
clear from the other reply I gave on your example. |
| 71 |
|
| 72 |
I'm not at all here to convince you; rather, I'm here to try to |
| 73 |
understand its meaning. If you do not want to clarify that or provide |
| 74 |
facts or references; then I agree to disagree with your opinion for |
| 75 |
adding that comment. Regardless of that, the mistake won't happen again. |
| 76 |
|
| 77 |
Thank you for the great work, your understanding and have a nice day. |
| 78 |
|
| 79 |
-- |
| 80 |
With kind regards, |
| 81 |
|
| 82 |
Tom Wijsman (TomWij) |
| 83 |
Gentoo Developer |
| 84 |
|
| 85 |
E-mail address : TomWij@g.o |
| 86 |
GPG Public Key : 6D34E57D |
| 87 |
GPG Fingerprint : C165 AF18 AB4C 400B C3D2 ABF0 95B2 1FCD 6D34 E57D |
Archives