[RFC] Creating Binary Only RPM's

[Kirsher, Jeffrey T]

During the creation of DKMS rpm's, we make binary-only and the default
source & binary rpm's.  With the updates to DKMS we have found that our
spec file no longer works to create DKMS rpm's and I have found that it
is because DKMS does not like a spec file which lists multiple source
files.  This was our way of including our documentation with the
binary-only rpm's.  In light of this, there are two possible resolutions
in my humble opinion:

 

Solution 1 - find an alternative way to copy the documentation files
included in the source to the binary-only tarball before creating a
binary-only rpm using the spec.  I have found this to be difficult but
not impossible.  So far, the attempts I have made have resulted in DKMS
not being able to build the rpm's and a non-descriptive error is
returned. "Error! There was a problem creating your rpm."

 

Solution 2 - create a new DKMS directive for the dkms.conf file which a
developer could list the documentation files in the source directory.
Then modify the mktarball -binaries-only option to include the
documentation file in a binaries only tarball.

 

In your opinion, what is the best solution?  

 

cheers,

Jeff

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.us.dell.com/pipermail/dkms-devel/attachments/20060330/5bb9c26a/attachment.htm