>
> You should package winecfg seperately in any case. In fact, I think you
> should package it with a completely different .spec (i.e. not part of the
> wine build process). It is not part of the wine sourcetree and building
> more than one thing in one rpm .spec never really works out very well. See
> RedHat's kernel RPM spec for an example of this, which incidently is
> probably a good .spec to look at if you want to know exactly what not to do
> when building an rpm. The whole specfile reaks of RedHat specific things
> and seems to be more tuned for RedHat's builds on their kernel building
> machine rather than make sense.
Winecfg will be part of the Wine source tree very soon,
I hope. And, Martin is (as we speak) revising it so that it
does not create an onerous packaging dependency, so that it
can be included in the binary distributions.
