[prev in list] [next in list] [prev in thread] [next in thread] 

List:       wine-devel
Subject:    Re : tool/wineconf problems
From:       eric.pouech () lemel ! fr (eric pouech)
Date:       1999-04-27 17:19:38
[Download RAW message or body]

from the technical part dealing with tools/wineconf, some questions though:
which perl version are you using ? would it be possible that you're still 
with perl 4 ?
the LC_ error messages come from perl itself (try removing use strict; but I
 doubt it'll change anything)
from the missing $ in var loop, I think it's linked to perl version (if it's
 necessary I'll revert loop local vars to there old syntax)


for the rest I agree with Juergend previous mail... wine developpers focus 
primarly on developping wine (which still need quite some work). It doesn't 
mean they don't care about TkWine, it does only mean that TkWine will not be
 their first tool for using wine, and thus are not able to provide much 
feeback. If I dare making a comparison with Linux, kernel hackers are not 
the one who build distributions... those are two different jobs, that 
required dedicated and involved people, of course working hand in hand

about the (legal) link between wine and TkWine... it may perhaps be a good 
idea not to apply wine licence to the configuration tools (wineconf, 
wineinstall, bug_report) so that they could be incorporated in source free 
distributions (or a sort of LWINE licence style) (Alexandre ?)

>
>
>--
>Jean-Louis Thirot
>CNRS UMR 6538 - Domaines OceaniiquesHi,
>
>tools/wineconf fails with latest CVS on my system:
>
>perl: warning: Setting locale failed for the categories:
>        LC_CTYPE LC_COLLATE
>perl: warning: Please check that your locale settings:
>        LC_ALL = (unset),
>        LC_CTYPE = (unset),
>        LC_COLLATE = (unset),
>        LANG = "us"
>    are supported and installed on your system.
>perl: warning: Falling back to the "C" locale.
>Missing $ on loop variable at /da3/DailyWine/wine/tools/wineconf line
>97.
>
>>From older version, I also had troubles with it, but it was crashing
>later and could produce at least a part of the drive section. I also
>think it's still too much linked to linux (refers to /proc/mounts are
>typical linuxism).
>I'd like to improve it, but .... it is licensed under wine's license, so
>I cannot include it in TkWine. That's not a problem for those users
>installing the sources, but I'm dont know where to find it when it comes
>to pre compiled packages...
>And above all, I hate to work on a part of my script that is into the
>tree and so I can't include it in my tree.
>
>I had almost no feed back after the last call on this list about it, but
>I think an application like wine deserve a Setup GUI... The huge number
>of people going to TkWine page (~5000 / week) and the large number of
>reports that I receive should convice that there is a need for this.
>This is just one exemple of the many limitations I have from not being
>incorporated into the tree....
>I can, of course, add a  pure tcl proc doing the same as wineconf
>does... but it would be sad to do that if it's not available for those
>who dowload the sources.
>
>This is just one of the many points where I'd like TkWine to interact
>much with wine itself. A dialog between configure and the script would,
>as an example, help me to set a progress bar. Id for make. This would
>requires slight changes in configure t so that it outputs (on stdout or
>in a file, no matter) some info on where it is (issuing a single word,
>where I know that there are N issues to come out, I can say how much
>work has been done so far). There are other examples.
>
>But above all: you know that all the docs manpage and so of the world
>will never prevent from basic repetitve questions. You need BIG letters
>somewhere to attract attention on something important. In a setup GUI,
>info comes ON SREEN and only the part of the info related to the current
>action... makes a big difference. Built in links to web resources is
>another feature that deserve attention (wine KB, dejanews, wine-howto,
>FAQ, manpage etc...).
>
>Last: TkWine dialogs and text are all into separate files... It will be
>easy to produce the setup in different languages (only the *.eng files
>will need to be duplicated)
>
>I still won't attach the script here, it's too large (450K) but it's
>still at
>http://panter.soci.aau.dk/~dailywine/tkwine/
>
>I'd like to understand why wine developpers shows so little interest in
>this tool. It's definitelly usefull to have graphical install, and
>especially for wine because it allows complicated config to be done by
>the user with no or small knowledge and efforts. If  you all says you
>don't wan't it, that fine, at least I'll know, even if it's looks crazy
>to me. But the sound of silence is surprising...
>
>Bye,
>Jean-Louis
>
>Institut Universitaire Europeen de la Mer
>Universite de Bretagne Occidentale
>Place Nicolas Copernic
>
>mail Jean-Louis.Thirot@univ-brest.fr
>tel (+33) (0)2 9849 8717
>fax (+33) (0)2 9849 9760
>
>
>
>
>


=========================================================================

[prev in list] [next in list] [prev in thread] [next in thread]