<div dir="ltr"><div><div>This sums it up pretty well, for a package with a 3rd party file, I can say my package also uses the same thing, maybe you can see the spec file as an example: <a href="http://jzygmont.fedorapeople.org/dosemu.spec">http://jzygmont.fedorapeople.org/dosemu.spec</a><br>
<br></div>Choosing the Fedora release you want to build is mentioned here: <a href="http://rpmfusion.org/Contributors#Import_your_package">http://rpmfusion.org/Contributors#Import_your_package</a><br><br></div>I usually test the rpmbuild process on my own computer, and keep editing the spec file until i'm satisfied with it enough to submit a build. It took me a lot of trial and error:) I found this page was very helpful: <a href="http://rpmfusion.org/Contributors">http://rpmfusion.org/Contributors</a><br>
<br><br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Sun, May 11, 2014 at 9:44 PM, Alec Leamas <span dir="ltr"><<a href="mailto:leamas.alec@gmail.com" target="_blank">leamas.alec@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="">On 05/11/2014 10:35 PM, Michal Altmann wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
BTW, I'd guess that unless you have some contacts the real bottleneck here<br>
is to become sponsored. Your goal here is to package this particular sw.<br>
However, becoming sponsored normally needs much more activity than that,<br>
sponsors sponsor people after they have been active in much more than just a<br>
single package. Also, it's sometime easier to get sponsored in Fedora than<br>
in rpmfusion, but then you need to submit more packages. See [1]. Note that<br>
if you're sponsored in Fedora this applies also to rpmfusion.<br>
<br>
</blockquote></blockquote>
Can you specified "much more activity" please?<br>
</blockquote>
<br></div>
Not really, my impression is that it depends on the sponsor which eventually might look into this. There is input on this in [1]<div class=""><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
We would like to<br>
package this software that consists from 4 separate packages and we<br>
are ready to contribute by other packages, for example, we would like<br>
to add Metalog that is not coded by us.<br>
</blockquote>
<br></div>
Before this is over, you would probably also need to contribute by doing informal reviews of other packages, as described in [1]. It's a question of demonstrating that you know the Guidelines.<div class=""><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I thing that we have no chance to get sponsored directly in Fedora<br>
because of non-free software as we found in guidelines. Maybe with 3rd<br>
software such as Metalog.<br>
</blockquote>
<br></div>
Yup, that how it worked for me once in a time.<div class=""><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I have a question about form of spec file for binary package. I am<br>
thinking about fixed dist and arch field. It is the right way to<br>
create SRPM directly for the target system, that can run the binaries<br>
? What Ferdora release are you prefere for the first review ?<br>
<br>
</blockquote>
<br></div>
You're better off using Rawhide i. e., the upcoming Fedora 21 . Depending on if/when this is completed, you might want to add a F20 version (current release) as well. This is really nothing you code into the spec, it's handled when you check it in into the VCS system (which is good o'l CVS on rpmfusion, git on Fedora). In those there is a specific branch for each Fedora version, so the differences such as the different sources is reflected there.<br>
<br>
The differences in this case between F20 and rawhide/F21 should normally just be one or two macro definitions unless you are using some cutting edge functionality which isn't available in both versions. You should try to make the spec as generic as possible, it helps a lot when maintaining it later.<br>
<br>
Cheers!<br>
<br>
--alec<br>
<br>
<br>
[1] <a href="https://fedoraproject.org/wiki/How_to_get_sponsored_into_the_packager_group" target="_blank">https://fedoraproject.org/<u></u>wiki/How_to_get_sponsored_<u></u>into_the_packager_group</a><br>
</blockquote></div><br></div>