Re: Notes R4 redraw problem

[Ian Pilcher]

Tony Lambregts wrote:
> Binary searching  is very efficient. As far as the theory goes I am 
> confident that a binary search for the bug should take 12 or or less 
> itinerations. The problem with this is that sometimes there are other 
> regressions that mask the original regression. I do not have lotus notes 
> (any version) but I do know about regression testing using CVS.

Tony -

If a binary search needs to be done, I'll do it.  (I can build and
install Wine in about 10 minutes on my system, so the compile time won't
be a problem.)  I am hoping to avoid it, however, because I'll have to
carve out and set up a complete test partition; I always use RPM to
install software on my production systems, and I don't want to spend the
time tweaking the SPEC file for each build.

Hopefully someone will be able to make sense of a message trace.

Notes R4 redraw problem

[Vincent Béron]

Le jeu 20/06/2002 à 14:16, Ian Pilcher a écrit :
> Tony Lambregts wrote:
> > Binary searching  is very efficient. As far as the theory goes I am 
> > confident that a binary search for the bug should take 12 or or less 
> > itinerations. The problem with this is that sometimes there are other 
> > regressions that mask the original regression. I do not have lotus notes 
> > (any version) but I do know about regression testing using CVS.
>
> Tony -
>
> If a binary search needs to be done, I'll do it.  (I can build and
> install Wine in about 10 minutes on my system, so the compile time won't
> be a problem.)  I am hoping to avoid it, however, because I'll have to
> carve out and set up a complete test partition; I always use RPM to
> install software on my production systems, and I don't want to spend the
> time tweaking the SPEC file for each build.
> Hopefully someone will be able to make sense of a message trace.
>
> ========================================================================
> Ian Pilcher                                           [e-mail]
> ========================================================================

Wouldn't it be possible to just install it in a scratch directory in the
home dir or in /tmp? That's what I do now for test builds, and it works
pretty well. I just use a wrapper script (yes, another) to wine, which
sets up the environment variables needed for it to work (PATH,
LD_LIBRARY_PATH, etc.).

In fact, I attach it here if you'd need it (or if somebody else needs
it). Of course, you also need to tell ./configure
--prefix=/where/you/want/it, then it's a normal make depend, make, make
install.

The first time, you'll also need to modify your wine.conf and install
the basic registry. And when you're finished with it, rm -rf (or F8 in
mc).

Vincent

Notes R4 redraw problem

[Francois Gouget]

On 20 Jun 2002, Vincent Béron wrote:
[...]
> Wouldn't it be possible to just install it in a scratch directory in the
> home dir or in /tmp? That's what I do now for test builds, and it works
> pretty well. I just use a wrapper script (yes, another) to wine, which
> sets up the environment variables needed for it to work (PATH,
> LD_LIBRARY_PATH, etc.).

You don't even need to install it at all. I have never installed Wine on
my system.

What I do is something along the lines of:

export WINE_ROOT=/home/fgouget/wine/wine
export LD_LIBRARY_PATH="$WINE_ROOT:$LD_LIBRARY_PATH"
export PATH="$WINE_ROOT:$WINE_ROOT/server:$WINE_ROOT/tools:$PATH"
export WINEDLLPATH="$WINE_ROOT/dlls"

Actually I have a script that does the above and which I use to pick one
Wine tree or another (". wenv wine" or ". wenv wine2", etc.).

I also have a ~/.wine directory with a fake_windows configuration that I
reuse from one time to the next. I also have it tarred so I can in
essence "rm -rf ~/.wine && tar xvfz dotwine.tar.gz".

--
Francois Gouget         [e-mail]        http://fgouget.free.fr/
In theory, theory and practice are the same, but in practice they're different.

Notes R4 redraw problem

[Vincent Béron]

Le jeu 20/06/2002 à 14:57, Francois Gouget a écrit :
> On 20 Jun 2002, Vincent Béron wrote:
> [...]
> > Wouldn't it be possible to just install it in a scratch directory in the
> > home dir or in /tmp? That's what I do now for test builds, and it works
> > pretty well. I just use a wrapper script (yes, another) to wine, which
> > sets up the environment variables needed for it to work (PATH,
> > LD_LIBRARY_PATH, etc.).
>
> You don't even need to install it at all. I have never installed Wine on
> my system.

The installation part makes it easy afterwards to install system-wide
when it works. But I agree you could do it after the testing, or not at
all.
> What I do is something along the lines of:
>
> export WINE_ROOT=/home/fgouget/wine/wine
> export LD_LIBRARY_PATH="$WINE_ROOT:$LD_LIBRARY_PATH"
> export PATH="$WINE_ROOT:$WINE_ROOT/server:$WINE_ROOT/tools:$PATH"
> export WINEDLLPATH="$WINE_ROOT/dlls"
>
> Actually I have a script that does the above and which I use to pick one
> Wine tree or another (". wenv wine" or ". wenv wine2", etc.).

What's the fundamental difference between WINE_ROOT/WINEDLLPATHS and
WINE_PREFIX?
> I also have a ~/.wine directory with a fake_windows configuration that I
> reuse from one time to the next. I also have it tarred so I can in
> essence "rm -rf ~/.wine && tar xvfz dotwine.tar.gz".

I also have an orig.tar.gz which is essentially the same thing, although
it also archives the etc dir. When I have a new test tree, I untar it,
then modify about 4 paths in it (I could use a sed script during the
installation, but I'm too lazy for now to sit down and write it).

Vincent

Notes R4 redraw problem

[Francois Gouget]

On 20 Jun 2002, Vincent Béron wrote:
[...]
> What's the fundamental difference between WINE_ROOT/WINEDLLPATHS and
> WINE_PREFIX?

WINE_ROOT is just an environment variable I use so that I don't have to
type the full path to the Wine sources over and over. It's even more
useful in my wenv script.

WINEDLLPATH tells Wine where to find the builtin Wine dlls. Here
/home/fgouget/wine/dlls

WINE_PREFIX tells Wine where to find its configuration file. By default
this is $HOME/.wine

--
Francois Gouget         [e-mail]        http://fgouget.free.fr/
           If it stinks, it's chemistry. If it moves, it's biology.
                  If it does not work, It's computer science.