On Wednesday 22 June 2005 12:21 pm, Dan Trainor wrote: > This software will not be released into the wild. It will be kept > strictly internal to the company which I work for. Based on this, and the fact that you seem to grasp all the issues, I say leverage the RPM tool any way you please. The only other danger is that someone who doesn't understand the issues, and is building RPMs that may be "released into the wild", may see your RPMs and copy the techniques you use. I've seen cases where someone builds a "bad" RPM, and later other teams use this bad RPM as their template and soon there are dozens of broken RPMs. The original packager may have understood the issues, and consciously made the RPM "bad" -- like you want to, but others just copy what they assume to be a good RPM. So maybe put a big disclaimer in your .spec. ;) -- Bart Whiteley
