1 |
On Mon, 10 Apr 2017 20:10:44 +0200 |
2 |
Michał Górny <mgorny@g.o> wrote: |
3 |
> |
4 |
> I don't see how attempting to discredit me is a fact regarding your |
5 |
> idea. |
6 |
|
7 |
You may assume what ever. I simply pointed out you are 1 of on a team |
8 |
of many. I have no requirement or duty to bring my ideas to you. If |
9 |
anything maybe the team lead. |
10 |
|
11 |
None the less, this issue crosses teams. Thus -dev ml and not directly |
12 |
with teams individually. Another thing you have missed. |
13 |
|
14 |
> |
15 |
> > |
16 |
> > Who do you think you are, to approach me or ANYONE such way? You are |
17 |
> > one person. The word team does not mean I, MGORNY.... |
18 |
> |
19 |
> Personal attack. Does not seem very factual. |
20 |
|
21 |
Stating a fact is not an attack. But the previous statement stands. |
22 |
Funny you send a copy to comrel. You start with insults much greater |
23 |
than any I lobbed your way. Yet instead of being man and taking what |
24 |
your shoveling out. You run off to the police.... |
25 |
|
26 |
Really funny, but I did not personally insult you as you did with your |
27 |
statements of ignorance, etc. If comrel was to act, it should be |
28 |
against you for your emails. Starting with your first. You should not |
29 |
approach anyone that way on a public list. |
30 |
|
31 |
> Except that the constant low level of posts on this list has resulted |
32 |
> in most of the developers avoiding it. If you cared about opinion of |
33 |
> the teams, you should have CC-ed them. |
34 |
|
35 |
You do not need to tell me or anyone to contact teams etc. Again if one |
36 |
team had a good idea. How would the other team know? |
37 |
|
38 |
Having redundant conversations on two lists with two groups is |
39 |
pointless. Kinda like spending time adding/removing targets from |
40 |
ebuilds. |
41 |
|
42 |
I am sorry you do not agree with my approach. But that is your opinion. |
43 |
|
44 |
> This is the best *working* way. I don't see you being able to figure |
45 |
> out a way that wouldn't randomly result in huge semi-random breakages |
46 |
> of dependency tree (as others have already pointed out), and that |
47 |
> wouldn't in the end require even more effort to fix them and keep |
48 |
> people able to upgrade anything without hitting huge conflicts. |
49 |
|
50 |
The idea here is to discuss better ways. This same thing happens to |
51 |
Java, Perl, and PHP. I think if those three can manage a better way. |
52 |
Python and Ruby can as well. |
53 |
|
54 |
Packaging things like Java is CONSIDERABLY more difficult than most |
55 |
other languages. If Java can do it, so can others. There used to be |
56 |
several Java VMs etc. There still are at least 3, Oracle, OpenJDK, and |
57 |
IBM. |
58 |
|
59 |
Go add JDK 9. See what that process is like and what all it entails. |
60 |
|
61 |
> Once again, you are focusing on attempting to discredit me by throwing |
62 |
> some random useless stats. This is how factual you are. |
63 |
|
64 |
Take it how ever you will. I am talking about WHO will do the work. |
65 |
Your commenting on something you are not doing yourself. That is not |
66 |
discrediting. Its showing you are not spending your time on this. But |
67 |
you expect others to. |
68 |
|
69 |
This is similar to the eapply thing of patch p1. Which I do not |
70 |
disagree with. But that also means allot of working patches need be |
71 |
modified just for that change. I do not like major changnes like that. |
72 |
When the people initiating the change are not doing the work. |
73 |
|
74 |
Pointing out that you are not the one managing python targets. Its |
75 |
showing you are not spending your time on this. If you were, I think |
76 |
you would feel otherwise. I think you would look to make things better |
77 |
since you would be doing minor edits on hundreds of ebuilds. |
78 |
|
79 |
That you are not doing that. Your trying to avoid something that may |
80 |
reduce work for others. Work that you are not doing. Yet your saying |
81 |
it is bad. Maybe let those who are managing the PYTHON_COMPAT in |
82 |
ebuilds to comment. |
83 |
|
84 |
I doubt they like that, or thing it is a efficient use of their time. |
85 |
|
86 |
> Again, you're attempting to discredit me, through some semi-relevant |
87 |
> oversimplification of history. And I'm afraid all that is proven by |
88 |
> this example is that your ebuild skills are seriously lacking and you |
89 |
> refuse to learn, and just rage quit. |
90 |
|
91 |
No that was a fact. You thought you were doing QA and making things |
92 |
better. You were not using the package nor testing out changes you were |
93 |
suggesting. I assuming you knew better allowed it, and others had to |
94 |
fix. |
95 |
|
96 |
I had a 1 line fix to correct an issue with logrotate permissions |
97 |
https://bugs.gentoo.org/show_bug.cgi?id=547442 |
98 |
|
99 |
Your series of comments here |
100 |
https://github.com/gentoo/gentoo/pull/101 |
101 |
|
102 |
Let to the entire revision of the ebuild, per your QA |
103 |
https://github.com/gentoo/gentoo/pull/154 |
104 |
|
105 |
Which you put in tree.... |
106 |
https://github.com/gentoo/gentoo/commit/9b00135f4696e539a3cbee711ac687f4f9ded105 |
107 |
|
108 |
However you broke things and missed others |
109 |
|
110 |
Bug you created |
111 |
https://bugs.gentoo.org/show_bug.cgi?id=577956 |
112 |
|
113 |
A user fixed with more fixes to the ebuild you missed. |
114 |
https://github.com/gentoo/gentoo/pull/3357 |
115 |
|
116 |
> |
117 |
> > Maybe just in mgorny's mind.... |
118 |
> |
119 |
> This is a clear personal attack, not a fact. |
120 |
|
121 |
Get over yourself. If you are concerned with being attacked. Maybe do |
122 |
not attack people to begin with. Your first post set the tone. Which |
123 |
another commented on before I did. |
124 |
|
125 |
> My point is that if you do not know how to write correct Python |
126 |
> ebuilds, you do not have a correct test case to even start planning |
127 |
> out your idea. |
128 |
|
129 |
I am not sure anyone but you knows how to write a correct ebuild from |
130 |
what I have seen. Given my experience with your QA on ebuilds. I |
131 |
seriously question it after having seen what all went on with Firebird. |
132 |
It was NOT the only one. |
133 |
|
134 |
Another package you voiced your QA over. You missed a grave issue that |
135 |
flameeyes/Deigo pointed out to me in a private email when I reached out |
136 |
to him for help. |
137 |
|
138 |
That FACT that you are missing things, creating other bugs, all in the |
139 |
name of your QA. The whole idea of QA is quality assurance. If your |
140 |
missing things, then your QA lacks QA.... |
141 |
|
142 |
But introducing new issues, which shows you did not even test your |
143 |
modifications. Not even sure how you can say its QA without testing.... |
144 |
|
145 |
> > |
146 |
> > > [1]:https://github.com/Obsidian-StudiosInc/os-xtoo/blob/master/dev-pytho |
147 |
> > > n/python-efl/python-efl-9999.ebuild |
148 |
> > |
149 |
> > That is new, and FYI mostly a copy form what is in TREE... Go diff |
150 |
> > and see for yourself. What ever issues I expect YOU mgorny to go |
151 |
> > fix in tree. Otherwise be quiet. |
152 |
> > https://github.com/gentoo/gentoo/tree/master/dev-libs/efl |
153 |
> |
154 |
> This is irrelevant + once again, a personal attack. If you don't want |
155 |
> me to judge your Python skills by the ebuilds you have in the |
156 |
> overlay, then why are you using the overlay to prove them in the |
157 |
> first place? |
158 |
|
159 |
You want to question my python ebuild skills on an ebuild I did not |
160 |
write. Then revert to a different argument. Ask yourself why did I even |
161 |
move it to my overlay than use in tree? What was the purpose? |
162 |
|
163 |
Did I provide ANY links to python ebuilds in my overlay as an example |
164 |
of who to write a python ebuild the correct way? No. I simple said I |
165 |
wrote a few recently, and that was NOT one. |
166 |
|
167 |
Maybe look at the ebuild. I guess you missed entirely.... |
168 |
|
169 |
# Based on ebuild from enlightenment-live overlay |
170 |
# Copyright 1999-2016 Gentoo Foundation |
171 |
https://github.com/Obsidian-StudiosInc/os-xtoo/blob/master/dev-libs/efl/efl-9999.ebuild |
172 |
|
173 |
How do you call it QA when you miss obvious things like that? |
174 |
|
175 |
> Finally, since you seem to be completely resistant to do at least some |
176 |
> basic research, and you keep trying to prove that I'm some developer |
177 |
> who is barely doing anything, lemme tell you a funny thing: I wrote |
178 |
> these eclasses, I designed this model and I was responsible for |
179 |
> switching it from opt-out to opt-in. |
180 |
|
181 |
How do you know what research I have and have not done? I never said |
182 |
you were doing nothing. I stated you are NOT the one adding/removing |
183 |
PYTHON targets from ebuilds. That is a fact. That is considerable work |
184 |
to add/remove new python targets. |
185 |
|
186 |
So you re-wrote the ebuilds, and are causing tremendous work for |
187 |
others. But you are not doing that work yourself. Yet standing by a |
188 |
design that you had some influence over. While still not doing the |
189 |
resulting work from said design. |
190 |
|
191 |
Again go modify a few hundred python packages to remove say 3.4. I |
192 |
think about 10-20 ebuilds in. You will be scripting and looking for |
193 |
another way.... |
194 |
|
195 |
> But then, all that work was obviously non-constructive, unlike |
196 |
> reviving the topic on the mailing list without doing any research or |
197 |
> simply asking the person who did it. |
198 |
|
199 |
What of your comments have been constructive? This discussion is not |
200 |
about everything to do with mgorny. I was pointing out you have not |
201 |
presented any alternative ideas. Nothing constructive, just criticism |
202 |
after starting with clear insults. |
203 |
|
204 |
I keep providing facts, and examples. |
205 |
|
206 |
-- |
207 |
William L. Thomson Jr. |