Good work.. Take a look at VMWare's spec file for some good ideas on how to have one
RPM that works with multiple
distributions. AFAIR, the VMWare RPM uses the pre/post-install and pre/post-remove
scripts to take care of the
differences in distributions.
Another good idea would be to build upon the wine.conf file generator. You could have
it install the wine.conf generator
along with wine and run the generator during post install. You could also provide a
script for someone to run the
generator. That way if the fstab changes with system configuration, the sysadmin
(user) can simply rerun the config
generator.
As far as paths to config files go, you should probably put wine.conf in /etc instead
of the usual /usr/local/etc or
/usr/etc. You could also include the base config file (without specific info about
the users sytem) in /etc/wine.conf.in
or maybe it would be better placed in the /usr/share directory. The sendmail package
comes to mind with it's M4
generated config file.
I haven't actually had a chance to look at your .spec file, but I am just sort of
throwing out ideas that I have gathered
from looking at various .spec files, and using the ideas to make my own.
-Dave
Marcus Meissner wrote:
> Hi,
>
> Since there are a lot of discussions to add "wine.spec" and related stuff
> to WINE I just send in the following patch with stuff I do use for building
> the WINE RPM in Caldera OpenLinux.
>
> The .spec file has OpenLinux specific macros inside, some work is needed
> to adapt it to RedHat or SuSE. Some files needs to be copied to SOURCES/ and
> some paths adapted.
>
> This is work done for Caldera Systems Inc. (Usual disclaimers apply.)
>
> Changelog:
> Contributed Caldera OpenLinux .spec file, icon and wrapper and setup
> scripts.
>
> Ciao, Marcus
