> Unfortunately, I guess rpms don't have such a system, so the decision of
> whether to make the package configure things interactively or not will be
> up to you non-debian people. Debian empowers users with choice...
well, now i see there is still some space for RPM package system
improvements...but i'm not going to improve it :-)
> > * do not support multiuser configuration YET
>
> We can support it. I've chosen a reasonable path - use tools/wineinstall,
> which has some basic multiuser support already. If we want to support
> multiuser better, we'd just improve wineinstall a bit... the multiuser
> aspect is thus up to the official Wine development effort, not up to the
> packagers.
i know. some patches to wine are required in order to support multiuser
properly. if that patches could be done in sensible time horizont, then
there's no reason to not support multiuser. but they are not done now.
> I thought about also creating a winecfg package... but it seems that
> you've written it with Tcl (yuck) and a few strange tools. Although "itcl"
> exists in Debian, neither "img", "mktclapp", or "exepak" seem to, and I
> don't know where their source distribution (.tar.gz) is... (not that I'd
> really enjoy becoming a package maintainer for Tcl stuff anyway)
tcl, tk, itcl and img are standard part of distributions like redhat,
mandrake etc. (older versions than winecfg need, at this time. but
that's going to change). mktclapp and exepak are very rare. that's why i
had to build RPMs for them. btw. all that stuff could be downloaded at
http://wine.codeweavers.com/winecfg.shtml in both RPM and SRPM format
(probably you know, just in case - source code is the part of SRPM
package).
martin
