On Fri, 2007-01-19 at 10:38 -0500, Matt Wringe wrote:
What is the proper way to handle upstream source tars that also contain
binary dependencies? This is very common with java packages.
Sorry if this is already covered in the guidelines, I couldn't find this
case mentioned anywhere.
Should the binaries be removed from the source tar and create a new
binary-less tar. This method has been used in the past, resulting in new
tars with -RHCLEAN added to the end of their names.
Or should the tar just be left alone, and have the a script inside the
spec scrub out the binaries?
You shouldn't need to alter the tar, unless those binaries are illegal
somehow. Have the spec remove the binaries in %setup, immediately after
The -RHCLEAN cases were when the tarball contained infringing/forbidden