On Fri, 17 Jan 2003, rcc wrote: > > > I like Xwine > > this looks so much nicer Well than, I can try packaging it. But should wine depend on it and run it automatically on first start (after the wine-config.pl)?
> I guess I don't get the logic behind mdk policy. Split libs from actual > programs and then but progs in lib packages because they happen to be > devel tools. Ah, it dawns on me, Thierry would probably suggest > splitting out the stuff into yet another package. Lets keep it like it is, at least untill the release. > Need sleep and there's a new wine package in > cooker which brutally dumped our thoroughly crafted mdkconf. > aha.Didn't see that yet. My cooker install is hopelessly behind. Want to do a fresh install anyway but lack the time. Thierry: any reasons for not applying some of the patches? Also: since Mark did some new stuff (regdefaults) that are working nice, and I fixed a few bugs in the config script, it is a bit awkward and more work to sync our stuff with this new release. A mail would have been nice. > Regarding the native vs fake win question: I use only the fake win, so I > could well live with a fake win as default. The screenshots at > codeweavers showed an option to use a fake win in the user's homedir. > Now, there's an idea... Think it makes sense? It would require every user to install a new windows program. Sometimes this makes sense. Sometimes it is a huge waste of diskspace. I usually (symbolic) link all the files of a program in a public dir to a subdir in my homedir. The result is that I can save personal stuff there, but the program files are shared. danny > > - Mark >
