Re: [Cooker] wine update for 9.1
rcc [EMAIL PROTECTED] writes: 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. exact :-) !
Re: [Cooker] wine update for 9.1
[EMAIL PROTECTED] writes: 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? there's no reason to not apply these patches. but viet has taken wine maintenance over me since he has access to zindoz. send him your patches with explanations as usual. 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. my coworker wasn't aware of your work :-(
Re: [Cooker] wine update for 9.1
sorry for this. the wine-mdkconf is still in the SRPMS I haven't really busted anything have I ? :o) Viet On Monday 20 January 2003 4:19 pm, Thierry Vignaud wrote: [EMAIL PROTECTED] writes: 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? there's no reason to not apply these patches. but viet has taken wine maintenance over me since he has access to zindoz. send him your patches with explanations as usual. 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. my coworker wasn't aware of your work :-(
Re: [Cooker] wine update for 9.1--slightly ot
rcc wrote: On Mon, 20 Jan 2003 18:30:17 + HA Quoc-Viet [EMAIL PROTECTED] wrote: sorry for this. the wine-mdkconf is still in the SRPMS I haven't really busted anything have I ? :o) don't know, I rarely install the cooker wine. It's just that Danny and I made some changes to the default config like enabling arts by default, putting mdk specific font dirs in, changed tmp dir, etc. You couldn't know about my new reg files as I only sent them to Danny for testing. They're still called wine.userreg and wine.systemreg but I decided to install them as system.reg and user.reg because I think there's no reason for deviating from wine's default naming scheme. I attach both reg files. They replace the cooker ones. Also, there's my autofs patch which I haven't yet submitted to winehq, they're probably not interested anyway. The patch shouldn't clash with other ways of mounting, it just tells wine to keep drives that are in config and have an automount line even if wine cannot stat their dirs, which is the case for autofs. Lastly, there's my mdkconf patch. When I can't make you merge rpms into fewer rpms for wine, I'd like to suggest splitting out the fake wine in /var/lib (wine-fakewin*.rpm ?)as I have that dir symlinked elsewhere and don't want it updated each time I install a new wine. I know that this proposal flatly contradicts my previous statements about libification... - Mark has your changes to wine made it so it can run windows based 3d modelling apps? like discreets 3d studio max, mcneel's rhino? only use I have for windows is these apps, which I can't get wine to run.
Re: [Cooker] wine update for 9.1
On Monday 20 January 2003 19:30, you wrote: sorry for this. the wine-mdkconf is still in the SRPMS I haven't really busted anything have I ? :o) course not:) I will try to integrate the few small changes Mark and I made with this version and send it to you tomorrow. Actually it might be very good that you became the new maintainer. I got the impression that Thierry has 2 much to do already :) Danny Viet On Monday 20 January 2003 4:19 pm, Thierry Vignaud wrote: [EMAIL PROTECTED] writes: 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? there's no reason to not apply these patches. but viet has taken wine maintenance over me since he has access to zindoz. send him your patches with explanations as usual. 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. my coworker wasn't aware of your work :-(
Re: [Cooker] wine update for 9.1
On Mon, 20 Jan 2003 18:30:17 + HA Quoc-Viet [EMAIL PROTECTED] wrote: sorry for this. the wine-mdkconf is still in the SRPMS I haven't really busted anything have I ? :o) don't know, I rarely install the cooker wine. It's just that Danny and I made some changes to the default config like enabling arts by default, putting mdk specific font dirs in, changed tmp dir, etc. You couldn't know about my new reg files as I only sent them to Danny for testing. They're still called wine.userreg and wine.systemreg but I decided to install them as system.reg and user.reg because I think there's no reason for deviating from wine's default naming scheme. I attach both reg files. They replace the cooker ones. Also, there's my autofs patch which I haven't yet submitted to winehq, they're probably not interested anyway. The patch shouldn't clash with other ways of mounting, it just tells wine to keep drives that are in config and have an automount line even if wine cannot stat their dirs, which is the case for autofs. Lastly, there's my mdkconf patch. When I can't make you merge rpms into fewer rpms for wine, I'd like to suggest splitting out the fake wine in /var/lib (wine-fakewin*.rpm ?)as I have that dir symlinked elsewhere and don't want it updated each time I install a new wine. I know that this proposal flatly contradicts my previous statements about libification... - Mark winefiles.tar.gz Description: GNU Zip compressed data
Re: [Cooker] wine update for 9.1
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
Re: [Cooker] wine update for 9.1
no, it's more of a frontend than a configuration program. Let it have its own menu entry and when the user starts it and then a winexe through it, wine-config will run. Ah, I see, the user might be tempted to configure wine before running an exe. Hmm, have to think about this. ok, but using it as a frontend sounds ok to me. Configure wine can be a menu entry added by the xwine package? it's not Thierry's name that's in the changelog. Guess HA Quôc-Viêt [EMAIL PROTECTED] got impatient. titi is maintainer and responsible :P maybe I'm seeing probs where there aren't any but this Let me see if I understand you: - registry changes are always written to home dir - if the installed win program is in global dir, some users miss reg entries if using a program not installed by them - if writing reg to globaldir=realwindir you can corrupt your realwindir, and therefore windows. Solution: 1) write config to globaldir!=windir. If this is possible. 2) change wine script to copy a fakeglobalreg from /var/lib/wine/globalreg to userhome dir at start. And copy the, potentially changed userreg to /var/lib/globalreg at exit. Ofcourse, both options are insecure. And user1 can screw user2's setup. But in windows it is the same. Danny
Re: [Cooker] wine update for 9.1
On Fri, 17 Jan 2003 14:21:52 +0100 (CET) [EMAIL PROTECTED] wrote: no, it's more of a frontend than a configuration program. Let it have its own menu entry and when the user starts it and then a winexe through it, wine-config will run. Ah, I see, the user might be tempted to configure wine before running an exe. Hmm, have to think about this. ok, but using it as a frontend sounds ok to me. Configure wine can be a menu entry added by the xwine package? have a look at it, it's really small and doesn't have many dependencies besides GTK. It offers configuration via neat combo boxes and I just noticed it even has a menu entry for launching winesetuptk (if you can push that into contrib). So you can have everything via xwine. http://darken.tuxfamily.org/pages/xwine_en.html i18n support is fairly rudimentary, the pot file created by xgettext is a mess of English and French. But maybe that will change if the app gets some publicity when it makes it into contrib or even the distro. Solution: 1) write config to globaldir!=windir. If this is possible. that's why I said I don't really know wine registry handling. Getting rid of the separate reg files is on the wine TODO list but who knows when it will be implemented. If globaldir reg means /etc/wine we's have to make it 664 for group wine. Don't know if that's a good idea. 2) change wine script to copy a fakeglobalreg from /var/lib/wine/globalreg to userhome dir at start. And copy the, potentially changed userreg to /var/lib/globalreg at exit. Ofcourse, both options are insecure. And user1 can screw user2's setup. But in windows it is the same. yea, any 3-year old can screw windows :P I think we can postpone this registry stuff, need to test this some more. For the time being, it would be nice to get our patches back into the package. My automount patch shouldn't collide with any other mount method as it basically is only an if config has automount line then keep drives. - Mark
Re: [Cooker] wine update for 9.1
Op woensdag 15 januari 2003 20:16, schreef Danny Tholen: On Wednesday 15 January 2003 19:41, rcc wrote: anyway, wine should pick up an existing win as long as it is in fstab. The dummy win is always there in /var/lib/wine. Changing from one to the other means changing one line in your .wine/config actually this failed on NT/2k/XP machines (I made an error in the script again, I am really no perl coder), but I have that fixed now (and a few other bugs which happen on 2k machines. It was usefull to install mdk at work:) Perhaps we can use the codeweavers wizard, isn't that one GPL? Danny Good idea. Its very easy, with current default install, to corrupt your existing windows when playing around with wine.
Re: [Cooker] wine update for 9.1
On Thu, 2003-01-16 at 13:46, Wim Horst wrote: Good idea. Its very easy, with current default install, to corrupt your existing windows when playing around with wine. How do you *tell* that you've corrupted Windows? =) -- adamw
Re: [Cooker] wine update for 9.1
How do you *tell* that you've corrupted Windows? =) Umm.. it doesn't crash correctly? :oP
Re: [Cooker] wine update for 9.1
On Thursday 16 January 2003 00:46, rcc wrote: so you can actually do work at work? :)=) actually, it was a collegues machine. never seen it. Is it that tcl/tk thingy I never got to run? yes, it didn't run? I like Xwine, though last time I checked the config editor was not implemented yet. I'll check it too when time permits. Another thing: do we have to split wine into 4 rpms? It's a pain to I think Thierry even wanted to split it in even more packages? I think wine and wine-devel would be sufficient. I've not yet seen an app that depends on libwine. Me neither, but it is consistant with the mdk lib policy. Some of the utils stuff seems better kept with wine proper. Like? Why move all these notepad, winemine stuff to the wine program? IMO they should be separate. And putting /usr/bin files like winegcc in a lib-devel package looks somehow not right to me. Well, it is used for development? Guess I do not agree, but perhaps you can convince me? Danny
Re: [Cooker] wine update for 9.1
On Thu, 16 Jan 2003 23:03:13 +0100 Danny Tholen [EMAIL PROTECTED] wrote: On Thursday 16 January 2003 00:46, rcc wrote: never seen it. Is it that tcl/tk thingy I never got to run? yes, it didn't run? not for me, but I didn't try very hard because I like Xwine this looks so much nicer Another thing: do we have to split wine into 4 rpms? It's a pain to I think Thierry even wanted to split it in even more packages? yes, I remember that I think wine and wine-devel would be sufficient. I've not yet seen an app that depends on libwine. Me neither, but it is consistant with the mdk lib policy. I feared you would say that And putting /usr/bin files like winegcc in a lib-devel package looks somehow not right to me. Well, it is used for development? 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. Guess I do not agree, but perhaps you can convince me? too late, in both senses. Need sleep and there's a new wine package in cooker which brutally dumped our thoroughly crafted mdkconf. 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... - Mark
Re: [Cooker] wine update for 9.1
Op dinsdag 14 januari 2003 09:37, schreef [EMAIL PROTECTED]: Is it possible to give it a first time wizard asking to use existing windows or creating a new windows directory structure. I will soon send an updated version to Thierry. d. On Tue, 14 Jan 2003, Vincent Meyer, MD wrote: Is an update of wine planned for 9.1? V.
Re: [Cooker] wine update for 9.1
On Wed, 15 Jan 2003 19:15:25 +0100 Wim Horst [EMAIL PROTECTED] wrote: Is it possible to give it a first time wizard asking to use existing windows or creating a new windows directory structure. sure, if you provide the code ;) anyway, wine should pick up an existing win as long as it is in fstab. The dummy win is always there in /var/lib/wine. Changing from one to the other means changing one line in your .wine/config - Mark
Re: [Cooker] wine update for 9.1
On Wednesday 15 January 2003 19:41, rcc wrote: anyway, wine should pick up an existing win as long as it is in fstab. The dummy win is always there in /var/lib/wine. Changing from one to the other means changing one line in your .wine/config actually this failed on NT/2k/XP machines (I made an error in the script again, I am really no perl coder), but I have that fixed now (and a few other bugs which happen on 2k machines. It was usefull to install mdk at work:) Perhaps we can use the codeweavers wizard, isn't that one GPL? Danny
Re: [Cooker] wine update for 9.1
On Wed, 15 Jan 2003 20:16:36 +0100 Danny Tholen [EMAIL PROTECTED] wrote: anyway, wine should pick up an existing win as long as it is in fstab. The dummy win is always there in /var/lib/wine. Changing from one to the other means changing one line in your .wine/config actually this failed on NT/2k/XP machines I have none of these, Win98 is the last MS OS ever to hit my HD :) (I made an error in the script again, I am really no perl coder), but I have that fixed now (and a few other bugs which happen on 2k machines. It was usefull to install mdk at work:) so you can actually do work at work? :)=) Perhaps we can use the codeweavers wizard, isn't that one GPL? never seen it. Is it that tcl/tk thingy I never got to run? I like Xwine, though last time I checked the config editor was not implemented yet. Another thing: do we have to split wine into 4 rpms? It's a pain to maintain. Though the unpackaged files feature in cooker helps somewhat. I think wine and wine-devel would be sufficient. I've not yet seen an app that depends on libwine. Some of the utils stuff seems better kept with wine proper. And putting /usr/bin files like winegcc in a lib-devel package looks somehow not right to me. - Mark
Re: [Cooker] wine update for 9.1
I will soon send an updated version to Thierry. d. On Tue, 14 Jan 2003, Vincent Meyer, MD wrote: Is an update of wine planned for 9.1? V.
Re: [Cooker] wine update for 9.1
On Tuesday 14 January 2003 09:37, [EMAIL PROTECTED] wrote: I will soon send an updated version to Thierry. d. On Tue, 14 Jan 2003, Vincent Meyer, MD wrote: Is an update of wine planned for 9.1? V. This is good news! Please make sure that it is compiled with CUPS support, and you will have a winner distribution for MS-office users!
[Cooker] wine update for 9.1
Is an update of wine planned for 9.1? V.
