winetest: build & publishing

[chmorgan at charter.net]

Lately I've been doing a lot of installer building with the NSIS installer(http://nsis.sf.net).  We could easily package winetest as a self-extracting and executing installer that was transparent to the user.  The installer would simply extract the actual winetest.exe to windows/temp, start it up and wait until it completed before exiting.  This should be transparent to winrash as well.

Chris


> 
> From: Jakob Eriksson <jakov at vmlinux.org>
> Date: 2004/04/23 Fri PM 02:24:17 EDT
> To: "Dimitrie O. Paun" <dimi at intelliware.ca>
> CC: Wine Development <wine-devel at winehq.org>, 
>         Paul Millar <paulm at astro.gla.ac.uk>,  Kevin Koltzau <kevin at plop.org>, 
>         Ferenc Wagner <wferi at afavant.elte.hu>
> Subject: Re: winetest: build & publishing
> 
> Dimitrie O. Paun wrote:
> 
> >  2. Uploading to SF
> >     This works nice now, but I'm afraid it may not when we
> >     have more than one person doing it. Namely, a release
> >     needs to be created, will that not fail if it already
> >     exists? Can we check that? If that's a problem, how are
> >     we going to deal with it? Kevin, can you please try to
> >     see if what happens if you upload two files (with
> >     differents sfutils invocations) into the same release?
> >  
> >
> 
> Can you also upload the exe?
> 
> Ferenc touched this issue slightly - if we want to point (maybe very 
> novice) users
> to a way to contribute to Wine - commandline option may be hard to 
> understand.
> A zipped file can also be an obstacle.
> It's very neat just to click "open" on an exe compared to unpacking a zip.
> 
> regards,
> Jakob
> 
> 
> 
>