On 05/26/2010 12:17 AM, Dmitry Timoshkov wrote:
> Scott Ritchie wrote:
>
>> I believe a reasonable alternative is to communicate directly with the
>> distro Wine packager and have them test your app against whatever
>> version of Wine they plan on shipping. That way you don't miss out on
>> good
On Wed, May 26, 2010 at 6:44 AM, Scott Ritchie wrote:
> On 05/25/2010 11:39 AM, Dan Kegel wrote:
>> On Tue, May 25, 2010 at 10:58 AM, Avery Pennarun wrote:
In either case, you probably want to bundle the Wine runtime
with the app rather than trying to run against whatever Wine
the
Scott Ritchie wrote:
> I believe a reasonable alternative is to communicate directly with the
> distro Wine packager and have them test your app against whatever
> version of Wine they plan on shipping. That way you don't miss out on
> good changes in Wine either.
That's unreasonable to put the
On 05/25/2010 11:39 AM, Dan Kegel wrote:
> On Tue, May 25, 2010 at 10:58 AM, Avery Pennarun wrote:
>>> In either case, you probably want to bundle the Wine runtime
>>> with the app rather than trying to run against whatever Wine
>>> the user has.
>>
>> I guess this is because wine is such a moving
On Tue, May 25, 2010 at 10:58 AM, Avery Pennarun wrote:
>> In either case, you probably want to bundle the Wine runtime
>> with the app rather than trying to run against whatever Wine
>> the user has.
>
> I guess this is because wine is such a moving target? It seems a
> shame to bundle a copy of
On Tue, May 25, 2010 at 1:47 PM, Dan Kegel wrote:
> On Tue, May 25, 2010 at 10:21 AM, Avery Pennarun wrote:
the winelib version was quite a flop too many problems
>>>
>>> Indeed. One should never release naked winelib apps.
>>> Instead, one should bundle the windows version
>>> with a p
On Tue, May 25, 2010 at 10:21 AM, Avery Pennarun wrote:
>>> the winelib version was quite a flop too many problems
>>
>> Indeed. One should never release naked winelib apps.
>> Instead, one should bundle the windows version
>> with a private copy of Wine, like Picasa (and
>> now at least one
On Mon, May 24, 2010 at 6:46 PM, Dan Kegel wrote:
> Max wrote:
>> the winelib version was quite a flop too many problems
>
> Indeed. One should never release naked winelib apps.
> Instead, one should bundle the windows version
> with a private copy of Wine, like Picasa (and
> now at least one
Max wrote:
> the winelib version was quite a flop too many problems
Indeed. One should never release naked winelib apps.
Instead, one should bundle the windows version
with a private copy of Wine, like Picasa (and
now at least one other app) have done.
Il 24/05/2010 02:39, Dan Kegel ha scritto:
I've long predicted that companies might use Wine
for a while to ship Linux-compatible products,
and later switch to a native build once they know
they have users. Well, now we have at least one
example of this: Bricscad (see http://www.bricsys.com ).
I've long predicted that companies might use Wine
for a while to ship Linux-compatible products,
and later switch to a native build once they know
they have users. Well, now we have at least one
example of this: Bricscad (see http://www.bricsys.com ).
This is a *good* thing, and validates somewha
11 matches
Mail list logo
