Greetings! My name is John S. Arntz I just signed up for this list and would like to introduce myself. I have used Fedora since Fedora 5 and love the packages that RPMFusion offers (Before RPMFusion I used FreshRPMs). I'm not a programmer, but I know enough to make a basic package. I plan to make my first package submission to Bugzilla soon, fceux, an NES Emulator based on FCE Ultra. My first question, though, where would be a good place to host the .spec and .srpm files? I don't have a website anwhere. I'm aware of sites like rapidshare, megaupload, qshare, and mediafire. But I'm not sure if those would be the best places to host the files. Once I am able to find a place to post them, I will take the plunge and file my submission for review. Also, the source contains gfceux which is a GTK Glade frontend based on GFCE Ultra. How should I handle packaging this? Should I make them two separate packages and submissions, since they are actually two builds included in the same tarball and have to be built separately, or as a sub-package of fceux? The .spec files that I have made are based upon fce-ultra and gfce-ultra's .spec files so as they exist now, I have them as two unique packages. You feedback is greatly appreciated.

On Sun, Jan 3, 2010 at 9:05 AM, Hans de Goede<j.w.r.degoede(a)hhs.nl> wrote: > On 01/03/2010 07:40 AM, John Arntz wrote: >> >> Greetings! >> >> My name is John S. Arntz I just signed up for this list and would like to >> introduce myself. I have used Fedora since Fedora 5 and love the packages >> that RPMFusion offers (Before RPMFusion I used FreshRPMs). I'm not a >> programmer, but I know enough to make a basic package. I plan to make my >> first package submission to Bugzilla soon, fceux, an NES Emulator based on >> FCE Ultra. My first question, though, where would be a good place to host >> the .spec and .srpm files? I don't have a website anwhere. I'm aware of >> sites like rapidshare, megaupload, qshare, and mediafire. But I'm not sure >> if those would be the best places to host the files. Once I am able to find >> a place to post them, I will take the plunge and file my submission for >> review. Also, the source contains gfceux which is a GTK Glade frontend based >> on GFCE Ultra. How should I handle packaging this? Should I make them two >> separate packages and submissions, since they are actually two builds >> included in >> the same tarball and have to be built separately, or as a sub-package of >> fceux? The .spec files that I have made are based upon fce-ultra and >> gfce-ultra's .spec files so as they exist now, I have them as two unique >> packages. You feedback is greatly appreciated. >> > > Hi John, > > Welcome! > > About hosting webspace for spec / srpms in review. Let me know when you have > a solution, I have the same problem :) > > Xavier, Perhaps we can provide some space on rpmfusion infra for rpmfusion > contributors ? Yeah, that's something we can work out.

On Sun, Jan 3, 2010 at 9:05 AM, Hans de Goede<j.w.r.degoede(a)hhs.nl> wrote: > About hosting webspace for spec / srpms in review. Let me know when you have > a solution, I have the same problem :) > > Xavier, Perhaps we can provide some space on rpmfusion infra for rpmfusion > contributors ? > Sorry for being naive but... is there a reason why adding an attachment to the review request is not a viable solution?

I know these, but AFAIK they only use Italian language: http://it.altervista.org/ http://xoom.virgilio.it/

I disagree with Hans. I would make two separate packages. I still don't know why upstream put them in the same tarball. They are different programs in every aspect: one is made in C and the other in python, they have different build systems and so on. There is no correlation between the two. I did ask upstream some time ago about releasing different tarball: one for fceux and the other for gceux. They told me they would have done so, but it seems they forgot. I think it is time someone else nag them :)

I uploaded here the two wips SRPMs I did a long time ago. Feel free to use what you need. http://www.webalice.it/musuruan/RPMS/wips/gfceux-2.1.0a-1.fc10.src.rpm http://www.webalice.it/musuruan/RPMS/wips/fceux-2.1.0a-1.fc10.src.rpm

On Sun, Jan 3, 2010 at 7:40 AM, John Arntz<jsarntz(a)yahoo.com> wrote: > Greetings! Welcome! > My name is John S. Arntz I just signed up for this list and would like to introduce myself. I have used Fedora since Fedora 5 and love the packages that RPMFusion offers (Before RPMFusion I used FreshRPMs). I'm not a programmer, but I know enough to make a basic package. I plan to make my first package submission to Bugzilla soon, fceux, an NES Emulator based on FCE Ultra. My first question, though, where would be a good place to host the .spec and .srpm files? I don't have a website anwhere. I'm aware of sites like rapidshare, megaupload, qshare, and mediafire. But I'm not sure if those would be the best places to host the files. Once I am able to find a place to post them, I will take the plunge and file my submission for review. I know these, but AFAIK they only use Italian language: http://it.altervista.org/ http://xoom.virgilio.it/ > Also, the source contains gfceux which is a GTK Glade frontend based on GFCE Ultra. How should I handle packaging this? Should I make them two separate packages and submissions, since they are actually two builds included in > the same tarball and have to be built separately, or as a sub-package of fceux? The .spec files that I have made are based upon fce-ultra and gfce-ultra's .spec files so as they exist now, I have them as two unique packages. You feedback is greatly appreciated. I disagree with Hans. I would make two separate packages. I still don't know why upstream put them in the same tarball. They are different programs in every aspect: one is made in C and the other in python, they have different build systems and so on. There is no correlation between the two. I did ask upstream some time ago about releasing different tarball: one for fceux and the other for gceux. They told me they would have done so, but it seems they forgot. I think it is time someone else nag them :)