On Mon, Mar 21, 2005 at 01:52:22AM -0500, Montgomery, Steven S wrote:

Rose-Hulman team here again. We're in the process of making our initial release of the Inkboard project. The first question is, how important is it to have binaries(RPMs) for a release? Will most people want the source code anyways?

The source code is the important thing. If the code's good then others will handle the packaging. For instance, if your code is integrated into mainline, then the Inkscape project will generate all the debs, rpms, ebuilds, exe's, etc. as usual. :-)

A related issue, we having problems creating the RPM. I'm not sure if it's a lack of understanding of RPMs or something to do with Inkscape on the dev machine. Here's the error it gives at the end of a "rpmbuild -ba": make[2]: *** [inkscape.desktop] Error 9 make[2]: Leaving directory `/usr/src/redhat/BUILD/inkboard-0.1' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/usr/src/redhat/BUILD/inkboard-0.1' make: *** [all] Error 2 error: Bad exit status from /var/tmp/rpm-tmp.68505 (%build)

RPM build errors: Bad exit status from /var/tmp/rpm-tmp.68505 (%build)

Actually I think you've missed the real error message; it'll probably be the one right before the Error 9 line. Can you post the entire build log?

Any thoughts or suggestions would be appreciated.

One thing to try is to run `make distcheck` prior to creating the RPM. That will analyze it for packaging errors.

The most common cause of errors with RPM's is file paths. RPM's get installed into an arbitrary directory location, so if parts of your build process assume that a file is in a particular location (like /etc or /usr/share/inkscape), that could potentially mess it up.

Hope this helps, Bryce