All,
I have written a RPM spec file (attached) by hand to see what I need to
include
in them when generating them automatically. The only things that this
spec file is missing is parsing on any files that need it and setting
permissions. I can now extract the permissions and parse information from
the
build, so adding that should be relatively straight forward. The only
problems remaining are:
1. RPM does not like out version naming scheme, it does not like "-" in
version names, I suggest that we should change to using a "." instead of a
"-". I also had to rename the directory in the source tar.gz file to reflect
the fact that I had changed the version number to include a . instead
of a "-", or else RPM could not find the source to build it.
2. When specifying --with-starlink to the ./configure script in the
source .tar.gz file, the build includes the additional path, but also
still keeps the path used in the nightly build:
g77 -g -O2 -I/home/vmwareshare/rhel30linux_i386/build/build-root/include
-I/home/ser/rpm/tmp/sla-2.4.12/star/include -fno-second-underscore -c zd.f
-fPIC -o .libs/libsla_la-zd.o
Here /home/vmwareshare/rhel30linux_i386/build/build-root/include was the
path
from the nightly build and /home/ser/rpm/tmp/sla-2.4.12/star/include was the
path derived from --with-starlink.
3. I do not know yet if the build generated any additional files that are
not
included in the manifest, up to now I have only found that the manifests
file is not included in the manifests. RPM warns you that some files are
missing, if you do not include them in the list.
Before you ask, yes this spec file does generate a relocatable RPM and you
can build and install the SRPM/RPM as a non-root user.
Before you ask again, yes I am still using EPM for the other package
management
systems, but due to popular demand, and the fact that it does not appear to
be that hard, I will also generate RPM spec files independent of EPM. Sorry
for before Brian, but you will have your SRPMs.
One last thing, the source in the star2html tar.gz file will not get passed
the ./configure stage, you get the error:
[ser@starpc star2html-1.4-7]$ ./configure
configure: error: cannot find sources (star2html.in) in . or ..
Well that is another Sunday up the spout, I must be mad!
Steve.
|