I use the gnu tools to maintain my projects for consistancy and have a .spec file for each of the various applications. It all seemed to work fine, until I decided to move my perl modules to a common place and call them Local. That caused me to end up with a bunch of dependencies like "perl(Local::xxx)". So I was able to dummy up a spec file to install those modules that would satisfy the requirements, but I also ended up with files with parens in them. I don't like to have to deal with special characters in file names for obvious reasons. Is there a way to specify an output file name in a spec file?
<br><br>I know I can always rename it, but I'd like to keep everything as standard as possible. <br><br>Maybe I could alias the dependency? I've noticed that some perl modules are distributed as rpms without the strange characters.
<br><br>I didn't specify the "requirement" for those modules, apparently rpmbuild dug them out from somewhere.<br><br>Anyway if someone could please point me in the right direction to get this resolved, I'd appreciated it.
<br><br>Thanks,<br>Jim.<br>