[Rpm-maint] How to change a file name that rpmbuild creates?

[Panu Matilainen]

On Thu, 27 Dec 2007, Jim Lynch wrote:

> 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?
>
> I know I can always rename it, but I'd like to keep everything as standard
> as possible.
>
> Maybe I could alias the dependency?  I've noticed that some perl modules
> are distributed as rpms without the strange characters.

Several options here, none of which require () in filenames :) What works 
best for you depends on your needs...

a) Package your local perl modules in rpm, this would give you properly
    tracked dependencies automatically.
b) If a) is not feasible for whatever reason, you can make a dummy package
    with no files in it that provides the  perl(Local::...) dependencies.
    Just add "Provides: perl(Local::xxx)" in the spec, no need to create
    such files.
c) Filter out the perl(Local::...) dependencies. Automatic perl
    dependency extraction is far from perfect and can add bogus
    dependencies to packages, some examples of this can be found
    here: http://fedoraproject.org/wiki/Packaging/Perl
d) Disable automatic dependencies completely and add requires + provides
    manually as needed.

> I didn't specify the "requirement" for those modules, apparently rpmbuild
> dug them out from somewhere.

Yes, rpmbuild by default extracts all sorts of dependency information 
automatically. It's a good thing normally, but can get in the way if 
everything isn't installed via rpm.

> Anyway if someone could please point me in the right direction to get this
> resolved, I'd appreciated it.

Hope the above helps,

 	- Panu -