Yuri Khan wrote:
> On Thu, Aug 6, 2009 at 19:50, Scott Ritchie wrote:
>> -Open Source and User Driven
>> +Open Source and User Driven
>
> Font size is not a valid excuse for skipping heading levels.
> Presentation issues should be handled in CSS.
>
>
I agree with this in principle, however I was
On Thu, Aug 6, 2009 at 19:50, Scott Ritchie wrote:
> -Open Source and User Driven
> +Open Source and User Driven
Font size is not a valid excuse for skipping heading levels.
Presentation issues should be handled in CSS.
On Tue, Oct 14, 2008 at 11:11 PM, Scott Ritchie <[EMAIL PROTECTED]> wrote:
> Just a small bug, but patchwatcher is complaining about my lostwages
> patch not applying.
Yeah, that's one of the many known bugs. When I
have time to work on patchwatcher, which isn't oft
Just a small bug, but patchwatcher is complaining about my lostwages
patch not applying.
Thanks,
Scott Ritchie
Somebody on wine-users asked us to clarify this, so:
diff --git a/templates/en/home_about.template b/templates/en/home_about.template
index aed434a..8af3209 100644
--- a/templates/en/home_about.template
+++ b/templates/en/home_about.template
@@ -26,5 +26,5 @@ at the User Guide.
Wine is free so
We have switched our website sources (previously known as lostwages),
over to git.
>From this point on I would prefer if all patches came from the git tree.
Refer to the git documentation on the website and wiki on how to prepare
patches with git.
The git module is called simply "website".
; Changelog: update WPF information and mailing address
>
>
>
>
> Index: en/contributing.template
> ===
> RCS file: /home/wine/lostwages/temp
it
> > Module name:lostwages
> > Changes by: [EMAIL PROTECTED] 2007/02/16 18:13:29
>
> Could we get rid of wineowner account? It makes it impossible to know
> who's doing the changes. Each user having access to the WineHQ box
> should have his own login.
>
> Welcome back Brian (if I read the wwn right).
>
On Fri, 16 Feb 2007, WineHQ wrote:
> ChangeSet ID: 30931
> CVSROOT: /opt/cvs-commit
> Module name: lostwages
> Changes by: [EMAIL PROTECTED] 2007/02/16 18:13:29
Could we get rid of wineowner account? It makes it impossible to know
who's doing the changes. Each u
On Sa, 2007-02-03 at 13:00 -0800, Scott Ritchie wrote:
> > The Sidenet - Script is still there.
> >
> I removed all traces of it from the wine wiki page I set up here, which
> the download-deb page should link to now:
> http://wiki.winehq.org/UbuntuAMD64
> I agree with you and Vitaly about this,
On Sa, 2007-02-03 at 01:33 -0800, Scott Ritchie wrote:
> I'll change the link to a page on our wiki with the same info and
> resend.
Please remove the tips for libxxf86dga from
http://wiki.winehq.org/UbuntuAMD64
winex11.drv dropped DGA Support at the end of July 2006
Thanks
--
By by ...
On Sat, 2007-02-03 at 21:52 +0100, Detlef Riekenberg wrote:
> On Sa, 2007-02-03 at 01:33 -0800, Scott Ritchie wrote:
> > > >
> > > > And as a Note on https://wiki.ubuntu.com/I386WineInAmd64 and
> > > > https://help.ubuntu.com/community/WineForAMD64
> > > >
> > > > The provided automatic installat
On Sa, 2007-02-03 at 01:33 -0800, Scott Ritchie wrote:
> > >
> > > And as a Note on https://wiki.ubuntu.com/I386WineInAmd64 and
> > > https://help.ubuntu.com/community/WineForAMD64
> > >
> > > The provided automatic installation script includes the sidenet-script.
> > > Please include a BIG WARNI
Scott Ritchie wrote:
> On Sat, 2007-02-03 at 00:06 -0700, Vitaliy Margolen wrote:
>> Detlef Riekenberg wrote:
>>> On Di, 2007-01-30 at 01:09 -0800, Scott Ritchie wrote:
+
+While there is currently no Wine package explicitly designed for
the 64-bit version
+of Ubuntu, there are
On Sat, 2007-02-03 at 00:06 -0700, Vitaliy Margolen wrote:
> Detlef Riekenberg wrote:
> > On Di, 2007-01-30 at 01:09 -0800, Scott Ritchie wrote:
> >> +
> >> +While there is currently no Wine package explicitly designed for
> >> the 64-bit version
> >> +of Ubuntu, there are several hacks that can b
Detlef Riekenberg wrote:
> On Di, 2007-01-30 at 01:09 -0800, Scott Ritchie wrote:
>> +
>> +While there is currently no Wine package explicitly designed for
>> the 64-bit version
>> +of Ubuntu, there are several hacks that can be used to install the
>> 32-bit package
>> +into the 64-bit distributio
On Di, 2007-01-30 at 01:09 -0800, Scott Ritchie wrote:
> +
> +While there is currently no Wine package explicitly designed for
> the 64-bit version
> +of Ubuntu, there are several hacks that can be used to install the
> 32-bit package
> +into the 64-bit distribution and have it function normally.
Hey, I'm not sure who is responsible for it, but could someone please
get my lostwages patch committed today? I've been getting a bunch of
emails about Ubuntu Edgy because the website hasn't been updated yet.
Thanks,
Scott Ritchie
On Thu, 28 Sep 2006, Mike McCormack wrote:
[...]
> They're still available at the old link:
>
> http://www.winehq.org/site/cvs
Yes, but this makes it harder to find them which is not going to foster
activity on the Wine documentation for instance!
> It would be nice to move the remaining modul
On Do, 2006-09-28 at 05:31 +0900, Mike McCormack wrote:
> > When switching the Instructions for the Wine tree
> > from cvs to git, the Instructions for the
> > additional modules (docs, lostwages, ...) got lost.
>
> They're still available at the old link:
>
>
On 9/27/06, Mike McCormack <[EMAIL PROTECTED]> wrote:
It would be nice to move the remaining modules to Git too, IMO.
And you can do all future web site matince IMO!
Tom
Mike
Detlef Riekenberg wrote:
When switching the Instructions for the Wine tree
from cvs to git, the Instructions for the
additional modules (docs, lostwages, ...) got lost.
They're still available at the old link:
http://www.winehq.org/site/cvs
It would be nice to move the remaining modul
On 9/25/06, Tom Wickline <[EMAIL PROTECTED]> wrote:
On 9/23/06, Mirek <[EMAIL PROTECTED]> wrote:
> >
> > Also Wine reports 64MB of video memory not 16MB
>
> I think there shuld be option in winecfg to set this, because it is not easy
to
> find how anyone can do that.
http://wiki.winehq.org/Usef
On 9/23/06, Mirek <[EMAIL PROTECTED]> wrote:
>
> Also Wine reports 64MB of video memory not 16MB
I think there shuld be option in winecfg to set this, because it is not easy to
find how anyone can do that.
http://wiki.winehq.org/UsefulRegistryKeys
Tom
On 23/09/06, Mirek <[EMAIL PROTECTED]> wrote:
> I also changed what benchmarks I had running at this years WineConf
> 3DMark2000, 3DMark2001SE and 3DMark2003... I have 3DMark2006 running
> and its beautiful, well beauty is in the eye of the beholder
> All of the test run in all three of the bench
el.template
===RCS file: /home/wine/lostwages/templates/en/wineconf/travel.template,vretrieving revision 1.18diff -u -p -r1.18 travel.template--- templates/en/wineconf/travel.template 2 Aug 2006 19:03:42 -
1.18+++ templates/en/wineconf/travel.templa
On 9/6/06, Paul Vriens <[EMAIL PROTECTED]> wrote:
On Wed, 2006-09-06 at 12:58 -0400, Tom Wickline wrote:
> Hello,
>
> If I overlooked something send me the link.
>
> Tom
>
> Changelog: update the press page
Hi Tom,
the latest edition of Tux Magazine (http://www.tuxmagazine.com/) has
some stuff
On Wed, 2006-09-06 at 12:58 -0400, Tom Wickline wrote:
> Hello,
>
> If I overlooked something send me the link.
>
> Tom
>
> Changelog: update the press page
Hi Tom,
the latest edition of Tux Magazine (http://www.tuxmagazine.com/) has
some stuff about CrossOver Office, Cedega and Wine.
Cheers,
On 9/6/06, Christoph Frick <[EMAIL PROTECTED]> wrote:
On Wed, Sep 06, 2006 at 10:21:42AM -0400, Tom Wickline wrote:
> -Jason Edmeades
> -Jukka Heinonen
> -Ove Kåven
> -Shachar Shemesh
> -Oliver Stieber
> -Greg Turner
would it not be more kind to move the "veterans" into their own section
instea
On Wed, Sep 06, 2006 at 10:21:42AM -0400, Tom Wickline wrote:
> -Jason Edmeades
> -Jukka Heinonen
> -Ove Kåven
> -Shachar Shemesh
> -Oliver Stieber
> -Greg Turner
would it not be more kind to move the "veterans" into their own section
instead of removing them at all? at least they managed to get
Tom Wickline wrote:
Hello,
News Wine 9.20 released
Tom
0a1,28
Please use "diff -u" for website patches.
--
Rob Shearman
Jeff Latimer wrote:
have. However after that I end up with this:
[EMAIL PROTECTED] wing]$ git rebase --continue
You must edit all merge conflicts and then
mark them as resolved using git update-index
I also have the options of git rebase --abort and git rebase --skip
which I am not sure of
Jeff Latimer wrote:
Mike I suppose that the problem is that wrapping your mind around git
and working out how to handle patches, especially as it takes time to
get them accepted, revert them and manage trees etc is difficult. I
don't know about other but I have had a number of perplexing and
On Fri, 2006-08-25 at 19:30 +0900, Mike McCormack wrote:
>
> Maybe we should move this to the Wiki too?
Maybe. But it changes seldom enough, and I think it will be
ugly to get all the formatting right in the Wiki format.
--
Dimi Paun <[EMAIL PROTECTED]>
Lattica, Inc.
"Colin Pitrat" <[EMAIL PROTECTED]> wrote:
How is it easier to do
cvs -z3 -d:pserver:[EMAIL PROTECTED]:/home/wine co -P wine
than
git clone git://source.winehq.org/git/wine.git wine
In both case, you just have to copy/paste the command line from the web
page.
Right. But if you compare the si
On Monday 21 August 2006 21:22, Jeff Latimer wrote:
> Mike I suppose that the problem is that wrapping your mind around git
> and working out how to handle patches, especially as it takes time to
> get them accepted, revert them and manage trees etc is difficult.
The way git does version control
* On Mon, 21 Aug 2006, EA Durbin wrote:
>
> > How is it easier to do
> > cvs -z3 -d:pserver:[EMAIL PROTECTED]:/home/wine co -P wine
> >
> > than
> > git clone git://source.winehq.org/git/wine.git wine
>
> because git doesn't seem to work on my machine,
EA, so this simply means my notes on taki
How is it easier to do
cvs -z3 -d:pserver:[EMAIL PROTECTED]:/home/wine co -P wine
than
git clone git://source.winehq.org/git/wine.git wine
because git doesn't seem to work on my machine, and I've never had problems
with the tried and trusted CVS, I'm familiar with CVS as are the majority of
EA Durbin wrote:
>
> if your not going to be submitting any patches its easier to get wine
> from CVS than GIT.
>
How is it easier to do
cvs -z3 -d:pserver:[EMAIL PROTECTED]:/home/wine co -P wine
than
git clone git://source.winehq.org/git/wine.git wine
In both case, you just have to copy/paste
Jeff Latimer wrote:
Mike I suppose that the problem is that wrapping your mind around git
and working out how to handle patches, especially as it takes time to
get them accepted, revert them and manage trees etc is difficult. I
don't know about other but I have had a number of perplexing and
If CVS goes, is there another way to see what patches have been applied to
the tree? The git does not seem to do that for me and cvs.winehq.org is a
fairly easy lookup.
Jeff
You can view the [EMAIL PROTECTED] over newsreader, but I still like the
web interface for CVS to view APPDB code
On 8/21/06, Jeff Latimer <[EMAIL PROTECTED]> wrote:
If CVS goes, is there another way to see what patches have been applied to
the tree? The git does not seem to do that for me and cvs.winehq.org is a
fairly easy lookup.
Jeff
To visualize the history just do something like this.
$ gitk -
Mike McCormack wrote:
Jeff Latimer wrote:
If CVS goes, is there another way to see what patches have been
applied to the tree? The git does not seem to do that for me and
cvs.winehq.org is a fairly easy lookup.
If you have a local git tree, "git whatchanged" will give you the
complete c
Jeff Latimer wrote:
If CVS goes, is there another way to see what patches have been applied
to the tree? The git does not seem to do that for me and cvs.winehq.org
is a fairly easy lookup.
If you have a local git tree, "git whatchanged" will give you the
complete commit history.
There's
Alexandre Julliard wrote:
Michael Stefaniuc <[EMAIL PROTECTED]> writes:
Are there any plans to get rid of CVS? I would guess keeping the CVS
tree sync from the git tree is low maintanance so it can be kept around
"forewever".
Yes, as long as it doesn't require any maint
Michael Stefaniuc <[EMAIL PROTECTED]> writes:
> But i also guess that he likes to receive more patches than less. For
> the casual/new Wine patch submitter CVS is easier to use. If those
> submitters do more Wine work they will see the light anyway and migrate
> to git ;)
More patches are good, b
On Mon, Aug 21, 2006 at 11:33:28AM +0200, Michael Stefaniuc wrote:
> > My changes to the website reflect that support for CVS may not last
> > forever...
> Are there any plans to get rid of CVS? I would guess keeping the CVS
> tree sync from the git tree is low maintanance so it can be kept
> arou
Mike McCormack wrote:
>
> Robert Shearman wrote:
>
>> I think we should leave the reference to the CVS tree page (but still
>> add a link to the Git tree). Some people find it easier to work with
>> CVS than Git.
>
>
> I think Alexandre would prefer to receive patch submissions in Git
> format,
Robert Shearman wrote:
I think we should leave the reference to the CVS tree page (but still
add a link to the Git tree). Some people find it easier to work with CVS
than Git.
I think Alexandre would prefer to receive patch submissions in Git
format, as they are easier to apply and waste le
> Date: Sun, 20 Aug 2006 14:45:03 +0300 (EEST)
> From: Saulius Krasuckas <[EMAIL PROTECTED]>
>
> > Date: Fri, 18 Aug 2006 11:36:31 -0500
> > From: EA Durbin <[EMAIL PROTECTED]>
> >
> > When trying to run git clone git://source.winehq.org/git/wine.git wine or
> > git clone http://source.winehq.or
> Date: Fri, 18 Aug 2006 11:36:31 -0500
> From: EA Durbin <[EMAIL PROTECTED]>
>
> 1.0.3 is the latest version in the ubuntu repository, even after
> uncommenting all the #deb lines in the apt config file and updating.
>
> When trying to run git clone git://source.winehq.org/git/wine.git wine or
> Agreed, CVS is much easier to use in my own opinion,
But in what way it is? For example I dislike managament of env-variables
at all. That's why I didn't like CVS :-p
In the way that the instructions on the wine page just worked, and for
familiarity purposes, git is rather new to me, and
> Date: Fri, 18 Aug 2006 08:18:43 -0500
> From: EA Durbin <[EMAIL PROTECTED]>
>
> > From: Robert Shearman <[EMAIL PROTECTED]>
> > Date: Fri, 18 Aug 2006 12:09:42 +0100
> >
> > I think we should leave the reference to the CVS tree page (but still
> > add a link to the Git tree). Some people find
er to navigate
than that of the git web interface.
From: Robert Shearman <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
CC: wine-devel@winehq.org
Subject: Re: LOSTWAGES: Replace references to CVS with Git
Date: Fri, 18 Aug 2006 12:09:42 +0100
Mike McCormack wrote:
Index: templates/en/developme
Mike McCormack wrote:
Index: templates/en/development.template
===
RCS file: /home/wine/lostwages/templates/en/development.template,v
retrieving revision 1.6
diff -u -p -r1.6 development.template
--- templates/en
On Tue, Apr 25, 2006 at 05:34:32PM -0400, Segin wrote:
> Marcus Meissner wrote:
...
> Let me hack at that patch a bit...
>
> Index: download.template
> ===
> RCS file: /home/wine/lostwages/templates/en/d
On Tue, 2006-04-25 at 17:34 -0400, Segin wrote:
>href="http://sourceforge.net/project/showfiles.php?group_id=6241&package_id=79444";>SUSE
> - binary and source .rpms for SUSE 9.0, 9.1, 9.2, 9.3, and 10.0
> + binary and source .rpms for SUSE 9.0, 9.1, 9.2, 9.3, 10.0, and
> 1
Marcus Meissner wrote:
Hi,
Adjust SUSE download entry to match what RPMs there are now.
Ciao, Marcus
Index: download.template
===
RCS file: /home/wine/lostwages/templates/en/download.template,v
retrieving revision 1.77
diff -u
Hello,
The first #6 is incorrect, please use this one
Tom
Changelog: move msacm.dll to Multimedia DLLs
Index: en/status_multimedia.template
===
RCS file: /home/wine/lostwages/templates/en/status_multimedia.template,v
retrieving
On Mon, 2006-02-06 at 02:47 -0500, Tom Wickline wrote:
> Change log: please see status_changelog for a complete change log.
> + ADD - Dmitry Timoshkov as worker to ICCVID
> + ADD - Dmitry Timoshkov as worker to MSRLE32
> + ADD - Dmitry Timoshkov as worker to MSVIDC32
Tom, I already mentioned it
> > + One exception,
> > +Unreal Tournament 2004, is available in a native Linux 64-bit
> > version, so
> > +nobody (except maybe a Wine hacker) should want to run the Windows
> > version
> > +anyway.
> Not 100% correct, there's also a Win64 version of Far Cry.
I didn't say there is no other
Am Donnerstag, 2. Februar 2006 18:37 schrieb Juan Lang:
> Due to a suggestion from Kate, rewrote the Win16/Win64 section.
>
> ChangeLog: Win32 has been the default for Wine for years, so say so
> + One exception,
> +Unreal Tournament 2004, is available in a native Linux 64-bit version, so
> +
Hello,
Tom
Change log: fix security.dll documentation link
Index: en/status_dlls.template
===
RCS file: /home/wine/lostwages/templates/en/status_dlls.template,v
retrieving revision 1.34
diff -u -r1.34 status_dlls.template
--- en
Jeremy Newman wrote:
ChangeSet ID: 22527
CVSROOT:/opt/cvs-commit
Module name:lostwages
Changes by: [EMAIL PROTECTED] 2006/01/24 14:26:23
Modified files:
templates/en : download.template
Log message:
based on patch from: Sven Paschukat <[EMAIL PROTEC
On Tue, 2006-01-24 at 21:01 +0100, Sven Paschukat wrote:
> as Vitaly noted it is not always clear that WineTools is not a
> requirement for using Wine, so let the users decide if they want to test
> or just want to use Wine.
> "... or if you want to get best chances of success ..."
I'd suggest
On 1/23/06, Vitaliy Margolen <[EMAIL PROTECTED]> wrote:
>
> Also Tom told me that he tried to contact winetools author and have not
> received response from him in almost a month.
I see Joachim sent a reply to the list, I suppose we should keep the
link and see
if we can find neutral ground.
Tom
Brian Vincent wrote:
Along similar lines, do we want to add a link for MacOS X going to the
Darwine page? It appears they're tracking our releases, at least for
PPC. It might clear up some of the questions coming to wine-devel about
whether Wine will be supported.
There is a pointer to Dar
Along similar lines, do we want to add a link for MacOS X going to the Darwine page? It appears they're tracking our releases, at least for PPC. It might clear up some of the questions coming to wine-devel about whether Wine will be supported.
-Brian
Monday, January 23, 2006, 3:16:41 PM, Chris Morgan wrote:
> On 1/23/06, Jeremy Newman <[EMAIL PROTECTED]> wrote:
>> Did we decide if we wanted to do this? I can't remember. A.D.D. you
>> know.
>>
>> On Fri, 2006-01-20 at 02:22 -0500, Tom Wickline wrote:
>> > Hello,
>> >
>> > Tom
>> >
>> > Changelog
Have we seen any response by the winetools guys as far as new revs and
support in #winehq? Vitaly would be a good person to ask about this I
think.
Chris
On 1/23/06, Jeremy Newman <[EMAIL PROTECTED]> wrote:
> Did we decide if we wanted to do this? I can't remember. A.D.D. you
> know.
>
> On Fri
Did we decide if we wanted to do this? I can't remember. A.D.D. you
know.
On Fri, 2006-01-20 at 02:22 -0500, Tom Wickline wrote:
> Hello,
>
> Tom
>
> Changelog:
> Remove third party downloads section from our download page
On 12/24/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> On Sat, 24 Dec 2005 04:22:19 +0100, Vitaliy Margolen
> <[EMAIL PROTECTED]> wrote:
>
> > As such, you are just _a_ user of Wine that fails to listen. And there is
> no point to speak with you about something that you are not even a part of.
On Sat, 24 Dec 2005 04:22:19 +0100, Vitaliy Margolen
<[EMAIL PROTECTED]> wrote:
As such, you are just _a_ user of Wine that fails to listen. And there is
no point to speak with you about something that you are not even a part of.
well since once again you prefer to ignore or not even read mo
Friday, December 23, 2005, 6:16:17 PM, Tom Wickline wrote:
> On 12/23/05, Vitaliy Margolen <[EMAIL PROTECTED]> wrote:
>> Friday, December 23, 2005, 11:36:16 AM, [EMAIL PROTECTED] wrote:
>> > I suppose everyone needs to feel important somewhere - some more than
>> > others.
>>
>> Before we get perso
On 12/23/05, Vitaliy Margolen <[EMAIL PROTECTED]> wrote:
> Friday, December 23, 2005, 11:36:16 AM, [EMAIL PROTECTED] wrote:
> > I suppose everyone needs to feel important somewhere - some more than
> > others.
>
> Before we get personal, and start discussing who did what, please stop by
> on #wineh
James Hawkins wrote:
encourage peer review. We value bug reports, comments, suggestions,
and criticisms, whether good or bad, so that we can make wine a better
application. Your comments infer that the developers aren't
interested in making wine easier for the end user, or that we are too
'har
On 12/23/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> On Fri, 23 Dec 2005 17:42:14 +0100, Chris Morgan <[EMAIL PROTECTED]>
> wrote:
>
> > I'm going to have to side with Vitaliy on this one. I've helped
> > dozens of users in #winehq that have had problems with wine due to
> > winetools since
Friday, December 23, 2005, 11:36:16 AM, [EMAIL PROTECTED] wrote:
> I suppose everyone needs to feel important somewhere - some more than
> others.
Before we get personal, and start discussing who did what, please stop by
on #winehq.
Then well'll talk.
On Fri, 23 Dec 2005 18:24:56 +0100, Vitaliy Margolen
<[EMAIL PROTECTED]> wrote:
There were case in US when family of someone killed with such a tool sued
manufacturer if said tool.
Yeah , and someone put thier poddle in the microwave and sued. Take that
sort of judgement too seriously and
Friday, December 23, 2005, 10:03:54 AM, [EMAIL PROTECTED] wrote:
> On Fri, 23 Dec 2005 17:33:05 +0100, Vitaliy Margolen
> <[EMAIL PROTECTED]> wrote:
>> I'm still insisting...and in most cases against the law.
> Everyone is responsible for thier own actions. Someone who makes a hammer
>
On Fri, 23 Dec 2005 17:33:05 +0100, Vitaliy Margolen
<[EMAIL PROTECTED]> wrote:
I'm still insisting...and in most cases against the law.
Everyone is responsible for thier own actions. Someone who makes a hammer
is not responsible for a murder comitted with it.
How does wine ensur
I'm going to have to side with Vitaliy on this one. I've helped
dozens of users in #winehq that have had problems with wine due to
winetools since we made the changes to remove the .config file.
Apparently winetools has been upgraded to work with 0.9x versions of
wine, this is great news although
Friday, December 23, 2005, 6:13:30 AM, Tom Wickline wrote:
> The Wine Tools maintainers have agreed to look into the problems that
> you have brought to the surface, can we please drop this subject?
No. I'm still insisting on removing winetools from the download page.
They are against the wine dev
On 12/23/05, Vitaliy Margolen <[EMAIL PROTECTED]> wrote:
> > On a slightly related note, in CrossOver we force a whole bunch of DLLs
> > to be builtin, like ole32, oleaut32, rpcrt4 and msi. Maybe we should do
> > the same for Wine?
> Well we could add them to the override list I guess. But I think
On Fri, 23 Dec 2005 06:58:03 +0100, Vitaliy Margolen
<[EMAIL PROTECTED]> wrote:
6. "Version"="win98" - that is wrong. Wine's default _is_ win2k.
It is right for the goal of the winetools. Again, this is why it's
titled "3rd Party Tools".
No, it's not. Some major changes have been made to l
Vitaliy Margolen schrieb:
I do not have Wine installed. All I have is wine symlink in my ~/bin dir.
And winetools could not find wine nor winecfg. So when I ran wt it
complained about that.
That's a situation we don't have expected. I will try to make a fix.
Mm looking at those checks I woul
On 12/22/05, Joseph Garvin <[EMAIL PROTECTED]> wrote:
>
> What usability? I've been reading the mailing list for a few months now,
> and the only extent of 'usability' discussions for wine has been over
> whether or not experienced linux geeks will be confused by options in
> winecfg. That's not us
Thursday, December 22, 2005, 12:04:52 PM, Robert Shearman wrote:
> Vitaliy Margolen wrote:
>>5. It adds some extra needless overrides to the registry, like
>> DLLOVERRIDES="*=native, builtin". Is there a reason for this? That
>> _is exactly_ what we, developers, trying to avoid.
>>
>>
> Actu
Thursday, December 22, 2005, 4:16:54 PM, Sven Paschukat wrote:
> Vitaliy Margolen schrieb:
>> 2. It can't use wine from the source tree (again for testing).
> It should. What were your problems?
I do not have Wine installed. All I have is wine symlink in my ~/bin dir.
And winetools could not find
James Hawkins wrote:
Usability is another rapidly progressing area of wine.
What usability? I've been reading the mailing list for a few months now,
and the only extent of 'usability' discussions for wine has been over
whether or not experienced linux geeks will be confused by options in
On Thu, 2005-12-22 at 09:43 +0100, [EMAIL PROTECTED] wrote:
> On Thu, 22 Dec 2005 02:59:57 +0100, Tom Wickline <[EMAIL PROTECTED]>
> wrote:
>
> > On 12/21/05, James Hawkins <[EMAIL PROTECTED]> wrote:
> >>
> >> As much as I appreciate the work you, Joachim, and others have put
> >> into winetools
Vitaliy Margolen schrieb:
So, Tom, could you please specify the place where I can redirect all the
people who having problems _with winetools_? To wine-users I presume? As
it looks to me that's the place where all the advertisement going on
about using winetools.
Why not to wine-users? Wineto
Vitaliy Margolen wrote:
5. It adds some extra needless overrides to the registry, like
DLLOVERRIDES="*=native, builtin". Is there a reason for this? That
_is exactly_ what we, developers, trying to avoid.
Actually, this makes sense for apps that install executables that are
coincidentl
Hi Vitaliy,
On Thursday 22 December 2005 18:32, Vitaliy Margolen wrote:
> Also had an interesting case last night: person had problems with
> winetools. When I asked the version, he said it's 3.0.9. So, there is your
> problem. Some one packaged winetools and made this version number.
This seems
Wednesday, December 21, 2005, 8:12:43 PM, Tom Wickline wrote:
> Winetools helps people run programs that they might not be able to and
> it helps them do that now. And that's what 99.9% of end users care
> about, can I run what I want to now? If the answer is no 99.8% of them
> will leave while .1%
On Thu, 22 Dec 2005 02:59:57 +0100, Tom Wickline <[EMAIL PROTECTED]>
wrote:
On 12/21/05, James Hawkins <[EMAIL PROTECTED]> wrote:
As much as I appreciate the work you, Joachim, and others have put
into winetools, we're getting closer to the point in time when
winetools needs to be phased out
On 12/21/05, Tom Wickline <[EMAIL PROTECTED]> wrote:
>
> Happy Holiday's
>
Happy Holidays to you too :)
--
James Hawkins
On 12/21/05, James Hawkins <[EMAIL PROTECTED]> wrote:
> On 12/21/05, Tom Wickline <[EMAIL PROTECTED]> wrote:
> >
> > So you agree that is currently needed, I believe it should stay until 1.0
> >
>
> The link or the program? Whether the program itself is needed is up
> to the users of winetools, an
On 12/21/05, Tom Wickline <[EMAIL PROTECTED]> wrote:
>
> So you agree that is currently needed, I believe it should stay until 1.0
>
The link or the program? Whether the program itself is needed is up
to the users of winetools, and they show that it's useful in the very
least, which I agree. Whe
On 12/21/05, James Hawkins <[EMAIL PROTECTED]> wrote:
winetools will
> eventually no longer be needed (which is a good thing!), and this is
> one of the first steps towards that process and wine 1.0.
So you agree that is currently needed, I believe it should stay until 1.0
Tom
>
> --
> James
1 - 100 of 212 matches
Mail list logo
