<br><br><div class="gmail_quote">2012/2/22 Simon Erat <span dir="ltr"><<a href="mailto:erat.simon@gmail.com">erat.simon@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br><br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">
Date: Wed, 22 Feb 2012 00:42:05 +0100<br>
From: Kevin Kofler <<a href="mailto:kevin.kofler@chello.at" target="_blank">kevin.kofler@chello.at</a>><br>
To: <a href="mailto:devel@lists.fedoraproject.org" target="_blank">devel@lists.fedoraproject.org</a><br>
Subject: Re: Package review: SC - Script Collection<br>
Message-ID: <ji1a4d$s5h$<a href="mailto:2@dough.gmane.org" target="_blank">2@dough.gmane.org</a>><br>
Content-Type: text/plain; charset="UTF-8"<br>
<br>
Simon Erat wrote:<br>
> What has been prepared so far:<br>
> * <a href="http://sf.net/p/seasc" target="_blank">http://sf.net/p/seasc</a> (source code, in sub projects)<br>
> * <a href="https://bugzilla.redhat.com/show_bug.cgi?id=795696" target="_blank">https://bugzilla.redhat.com/show_bug.cgi?id=795696</a> (review request)<br>
> * <a href="http://sea.hostingsociety.com/rpm.sc.template.spec" target="_blank">http://sea.hostingsociety.com/rpm.sc.template.spec</a><br>
> * <a href="http://sea.hostingsociety.com/changelog" target="_blank">http://sea.hostingsociety.com/changelog</a><br>
> * <a href="http://sea.hostingsociety.com/sc-0.2.0.tar.gz" target="_blank">http://sea.hostingsociety.com/sc-0.2.0.tar.gz</a> (its a bash script,<br>
> nothing to compile)<br>
> * <a href="http://sea.hostingsociety.com/sc-0.2.0-2.fc16.noarch.rpm" target="_blank">http://sea.hostingsociety.com/sc-0.2.0-2.fc16.noarch.rpm</a><br>
<br>
First observations:<br>
* Name is too short. A package with such a long history as "ed" can get away<br>
with a 2-letter name, but yours not really. It's just asking for conflicts…<br>
* The specfile name is not valid (should be %{name}.spec, not<br>
rpm.%{name}.template.spec).<br>
<br>
Kevin Kofler<br></div><div class="im">
--<br>
devel mailing list<br>
<a href="mailto:devel@lists.fedoraproject.org" target="_blank">devel@lists.fedoraproject.org</a><br>
<a href="https://admin.fedoraproject.org/mailman/listinfo/devel" target="_blank">https://admin.fedoraproject.org/mailman/listinfo/devel</a><br>
<br>
End of devel Digest, Vol 96, Issue 104<br>
**************************************<br>
</div></blockquote><br></div>* IF "sc" really is too short (noone reported that it conflicts any other name), an obviously alternative would be seasc, which is the projects name on sourceforge.<br>* The rpm.sc.template is 'invalid' as that is the file i use as template, which will get CAT to makerpm's ~/rpmbuild/SPEC/sc.spec, and getting the changlelog appended.<br>
This procedure can be reviewed in $scDir/system/<a href="http://dev.sc" target="_blank">dev.sc</a> which contains the self-distributing code.<br>But since 'sc' is too short (it may, but does not yet) conflict other things, there has to be another %{name} anyway.<br>
<br>The project is currently located in a folder named "sc-fedora" which could be an alternative name either.<br>So either: ssc or scf (which i think already exists and therefore DOES conflict), or something i dont want the users to type: script-collection.<br>
<br>Anything of this acceptable /negotiateable?<span class="HOEnZb"><font color="#888888"><br><br>Simon Erat<br>
</font></span></blockquote></div>What am i supposed to do now?<br>Just rename the spec file? And all will be fine?<br><br>Figured, that SC is not used in Fedora, but probably in other distros. Point taken.<br>SSC might conflict either, but googling "seasc" brings up my <a href="http://sf.net">sf.net</a> project home as 2nd result, first is a username.<br>
<br>In conclusion, the next 2 steps are:<br>1) Rename all inside my scripts from sc to seasc.<br>2) Rename the specfile, allthuogh i'm modifying it before its usage (over/write to ~/rpmbuild/SPEC/seasc.spec and appending changelog)<br>
<br>Does this sound good to go?<br>Or am i missing something i could do along the massiv renaming?<br><br>I'll be awaiting confirmation or additioninal tasks to this message, before i actualy rename everything.. :(<br>
<br>Thank you.<br>sea aka Simon A. Erat<br>