> Should we be performing the config file check inside wine at startup?
Already wine is a wrapper that starts wine-pthread or wine-kthread, and don't
forget about performance.
>For this config check should we do something like:
>if no config -> copy over default config
>
>if windows drive doesn't
- Where should we be installing the base config files? Can we put them in the
libs directory with the rest of the wine libs? I was looking at modifying
documentation/Makefile.in to take care of this
- After seeing Marcus' email I realized that I completely forgot about the
issue of the user n
On December 17, 2003 07:57 am, Chris Morgan wrote:
> >I don't like the idea; I much prefer the idea of copying
> >them from somewhere
> >in /etc, as redhat does. The default config file in /etc
> >can then be
> >modified so that it matches the distribution (redhat have
> >their cd at
> >/mnt/cdrom
> Trading off configurability with usability seems fine to
> me.
We aren't as one can tweak things with winecfg if he wants/needs to
> The goal is to solve both
> the lack of config files for binary installs, fixed by the
> patches that Che has in his rpm package and Marcus has for
> Suse, an
Trading off configurability with usability seems fine to
me. I doubt you'd hear much complaining about the default
configuration not being correct and users wanting to edit
it. In either case if the same can be accomplished
without including the config files in the binary then that
of course
>The less modification to the install process the better.
>If there was a single location the files could be
>installed to that would work for all distros I think this
>is the route to head in.
You can install the files anywhere, as long as the location isn't already used
for something else, /e
> Read documentation/PACKAGING, I had it added to CVS with most ideas already
> inside on Jun 27, 1999.
I've read this. I also had a look at the recording of your speech about wine
packaging at wineconf 2002.
I've followed the indications of documentation/PACKAGING at lines 385-404,
mainly for usab
I don't like the idea; I much prefer the idea of copying
them from somewhere
in /etc, as redhat does. The default config file in /etc
can then be
modified so that it matches the distribution (redhat have
their cd at
/mnt/cdrom) and it can be modified by the sysadmin
The less modification to
On December 16, 2003 06:39 pm, Chris Morgan wrote:
> I was chatting with Rudolf Kastl(che on #winehq) and he was mentioning the
> things that he was doing for the rpm package. One of the patches he
> applies to wine prior to packaging it is a patch that creates local user
> config files if they do
On Wed, Dec 17, 2003 at 10:51:42AM +0100, Ivan Leo Murray-Smith wrote:
> >I was wondering if it would make more sense during the compile process to take
> >the default configuration files, config, system.reg, user.reg and userdef.reg
> >and convert these to binary form and compile them into the w
> If wine-c is stored uncompressed, it's easier for a site admin to modify
> it for all its users.
True, but this shouldn't be necessary. Also any global configuration should be
done via winecfg.
> Also, there are a couple places in Wine which are dependant on how the
> underlying distribution is s
Le mer 17/12/2003 Ã 05:52, Ivan Leo Murray-Smith a Ãcrit :
> >I was chatting with Rudolf Kastl(che on #winehq) and he was mentioning the
> >things that he was doing for the rpm package. One of the patches he applies
> >to wine prior to packaging it is a patch that creates local user config files
>I was chatting with Rudolf Kastl(che on #winehq) and he was mentioning the
>things that he was doing for the rpm package. One of the patches he applies
>to wine prior to packaging it is a patch that creates local user config files
>if they don't exist.
His patches modify wine/libs/wine/config.
>I was wondering if it would make more sense during the compile process to take
>the default configuration files, config, system.reg, user.reg and userdef.reg
>and convert these to binary form and compile them into the wine binary
>itself. We could detect the lack of these files at startup and
I was chatting with Rudolf Kastl(che on #winehq) and he was mentioning the
things that he was doing for the rpm package. One of the patches he applies
to wine prior to packaging it is a patch that creates local user config files
if they don't exist. This helps end users as they don't have to w
15 matches
Mail list logo
