Re: RPM packaging errors

--On Tuesday, October 12, 2004 5:35 AM -0700 Jeff Smith 
<whydoubt@xxxxxxxxx> wrote:
> mdbtools-0.6-0.pre1.tar.gz comes with an older version of ltmain.sh
> (1.5).  With it, the '.so' is missing from the file names.  With version
> 1.5.6, the correct files are created (for me at least).  If you have
> libtool installed, you may be able to copy the file from
> /usr/local/share/libtool/.
Ok, I got around that by symlinking the current version into the build 
directory. I could probably go as far as regenerating configure with 
autoconf but most packages don't do that.
I also fixed the name mdb-dump to mdb-hexdump.

With that done, the build completes and I'm left with these "unpackaged" 
files:
  /usr/bin/mdb-import
  /usr/bin/mdb-prop
  /usr/bin/prcat
  /usr/bin/prdata
  /usr/bin/prdump
  /usr/bin/prindex
  /usr/bin/prkkd
  /usr/bin/prole
  /usr/bin/prtable
  /usr/bin/unittest
  /usr/bin/updrow
  /usr/include/connectparams.h
  /usr/include/gmdb.h
  /usr/include/mdbodbc.h
  /usr/include/mdbprivate.h
  /usr/include/mdbver.h
  /usr/lib/pkgconfig/libmdb.pc
  /usr/lib/pkgconfig/libmdbsql.pc

Should all of these be left out of the RPM? Or is this an oversight?

Right now the subpackages include base, devel, odbc, and gui. I'd guess the 
utilities in /usr/bin should go in base, and the pkgconfig stuff in include 
and lib should go in devel. Does any of it go in odbc or gui, or get left 
out altogether?
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl