On Tue, Oct 31, 2000 at 03:57:29PM -0500, Dimitrie O. Paun wrote:
> From: "Jeremy White" <[EMAIL PROTECTED]>
>
> > 1. At package install time, should we create a
> > global wine.conf?
> >
> > View 1: No - we supply something like
> > wine.conf.template, and then walk
> > the user through using winecfg of wineconf
> > to get their own .winerc.
> >
> > View 2: Yes. We autobuild a global wine.conf
> > file during the install process.
> > With debian, we can do this somewhat
> > elegantly due to debconf.
>
> There is not much difference between these two: even in the
> second case, if the user wants to customize some of the
> settings, he will have to copy the global file into their own
> .winerc file. In other words, the two cases are almost the
> same, the difference being that in the second one we do the
> copying lazily.
>
> I would say the issue is wether or not we inherit settings
> from the global file or not.
Hmm, I don't think so.
I think the main question is how to make it as easy as possible to end users
to configure Wine.
And if they have a global wine config file, but no local one and having
problems with drive settings because of that, then this is not good,
IMO.
This is why we might want to auto-launch a configuration program if no local
wine config file is detected.
But on the other hand I didn't really think about that yet.
> > 2. (Not yet discussed) - What packages do we provide?
> >
> > Marcus provides one - Wine.
> >
> > Ove provides five - libwine-dev, libwine, wine-doc, wine-utils,
> > and wine.
> >
> > I would argue that Marcus provides too few, and that Ove
> > provides too many.
>
> True. I agree with your suggestion, but I don't like the names. The current
> naming convention is to use -devel for the development package, so I
> would say:
> wine -- for end users, would allow to run winelib/win32 apps
> wine-devel -- for developers of winelib apps
Err, sorry. This is a distro issue.
Debian's global naming convention is -dev.
If others like to use -devel, fine with me.
And IMO it's the very same with the number of package parts.
If other distributions intend to have two packages, fine.
But IMO Debian has always split programs into more pieces.
> > 3. Concern - winecfg dependencies
> >
> > When designing winecfg, we chose Tcl/Tk, partly because
> > that's what TkWine used, and we were trying to expand on that,
> > and partly because we didn't have a clear alternative.
>
> Python would have been so much nicer...
Hmm, no idea here... ;-)
> 6. With/without a windows installation
>
> I think we should have a script that would allow the user to easily change
> between a configuration pointing a windows installation and one without a
> real windows install. Basically this idea can be generalized in a number of
> ways, but the idea is to allow the user to make this sort of change very easily.
That's a rather good idea, yes.
I've been switching between windows and no-windows several times, too.
Andreas Mohr
