Re : Re : How about this replacement of WINE.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> >> Patching kernels and building modules is no big thing but patching and 
> >> compiling wine, being tied to an older version or constantly upgrading and 
> >> redoing this might be a bit too 
> >> much.
> >> 
> > Why being tied to an older version ?
> > 
> Stable versus unstable kernel releases, maybe?
You have a point there.

> > The fact is that the project is not that old,
> > thus earlier versions of wine/kernel havent been tested at the moment.
> >
> > 
> Which project? Wine is very old, going back to the early 1990s, when 
> Linux was released to the public. You also have to be aware that Wine 
> is the source for several forks, one is for the Mac which I use.
I know, beeing one of them for some times :)
*Linux Unified Kernel* project is not that old.

> 
> > Btw, many apps need a specific dependancy for older libraries.
> > 
> That is very true. We in the industry call this 'dll hell' as some 
> programs will only run with certain versions of some .dll files.
> 
> 
> James 
> McKenzie

Regards,
Sylvain Petreolle



[Index of Archives]     [Gimp for Windows]     [Red Hat]     [Samba]     [Yosemite Camping]     [Graphics Cards]     [Wine Home]

  Powered by Linux