Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=498736 --- Comment #5 from Mamoru Tasaka <mtasaka@xxxxxxxxxxxxxxxxxxx> 2009-05-02 14:20:31 EDT --- (In reply to comment #3) > 1. ucommon is NOT the same as commoncpp. Both can also co-exist. ucommon is > technically a successor package to commoncpp. - The reason I am asking you about this is that I see the term "commoncpp" in URL. I guess the upstream URL for this is http://www.gnutelephony.org/index.php/UCommon > 2. I use a macro for that because ucommon can be built in a deeply embedded > profile without using libstdc++, so if in theory one uses to spec to > cross-compile such a target, one can force libstdc++ off. - Well, okay. > 3. I define %version and %release this way because I have a build script to > override (autogenerate) values for a rpmbuild through the --define option (also > why I have %uses_...). - Please don't do this but directly define version, release in Version, Release. > 4. Remaining items look also easy enough to resolve. How do I submit an > updated spec file? - Upload the new spec file and new srpm on somewhere. spec file can be overwritten on the URL you used on the original post, however please make it sure that you change the Release number every time you modify your spec file to avoid confusion (so the filename of srpm will change every time you modify your spec file). -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. _______________________________________________ Fedora-package-review mailing list Fedora-package-review@xxxxxxxxxx http://www.redhat.com/mailman/listinfo/fedora-package-review