On Fri, 18 Jun 2010, m0n0 wrote:
Hello, Probably this was told several times before, maybe it's even the issue Keith talked several times before - but how should I provide Binary packages of an program (not an lib)? Should I provide different RPM's for different machines? Keith talked about Multi-Architecture RPM's containing libs AND Executables, but providing RPM's that just contain executables is also unclear. Of course it is no big problem creating different spec files, but that is not good when things have to be changed in the spec file.
Rather than post it, here is 'basically my current thought: http://atarimint.blogspot.com/2010/06/multi-target-sparemint-rpm-thoughts-how.htmlI have just rebuilt RPM to verify it works and compiles with the newer tools. Next I'm going to modify the package to add those targets, so, in most cases only 1 spec should ever be needed.
The biggest problem arises when a package is a mixture of libs and binaries, not sure, yet, what to do for it. Multiple dev libs for each target will cause RPM issues since headers will conflict between them if you want multiple CPU targets.
Keith