<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 07/15/2015 12:05 PM, Michael
Schwendt wrote:<br>
</div>
<blockquote class=" cite" id="mid_20150715180539_30a18381_noname"
cite="mid:20150715180539.30a18381@noname" type="cite">
<pre wrap="">On Wed, 15 Jul 2015 11:05:40 -0400, Przemek Klosowski wrote:
</pre>
<blockquote class=" cite" id="Cite_2040538" type="cite">
<pre wrap="">I do understand where you're coming from: the Fedora workflow is quite
complicated
</pre>
</blockquote>
<pre wrap="">What exactly do you find "quite complicated"?
<a class="moz-txt-link-freetext" href="https://fedoraproject.org/wiki/Package_Review_Process">https://fedoraproject.org/wiki/Package_Review_Process</a>
</pre>
</blockquote>
I was responding to Les' comment about the tools that one needs to
use in order to package something: RPM, VCS, i18n, lib/autotool,
COPR, Bodhi, mock, etc. Don't get me wrong---I am not saying that
there's anything wrong with the tools, just that they seem easy to
those who already mastered them, but may be intimidating to the
uninitiated. <br>
<br>
This is my point, actually, that it's hard for a packaging pro to
appreciate the confusion of a newbie. Some kid-glove treatment, and
ELI5 tutoring/mentoring might help.<br>
</body>
</html>