Support for binaries that were abandoned by M$, and maintenance hell?
meissner at suse.de
Wed May 11 03:57:39 CDT 2005
On Tue, May 10, 2005 at 11:44:03PM -0500, Dustin Navea wrote:
> The discussion on 16-bit support for cards.dll led me to an interesting
> As I said, soon we will be not necessarily abandoning 32-bits, but
> writing more 64-bits.. Sure we have separation to keep things apart,
> but wine is starting to get loaded down with things that only a small
> minority of users need anymore.. Perhaps it is time (just another idea)
> to copy out the 16-bit code into it's own project? That way we can
> organize things more efficiently, and at the same time, reduce 1)
> download time of wine, and 2) compile time.
> Of course, we would still leave 16-bit support in the main project, but
> we would no longer maintain it there.. We could maintain it in wine16....
> </flame war first shot>
> Comments? Suggestions? Flames??? Bring it ;-)
16bit support is deeply integrated into the WINE core and not easy to extract.
And it is usually not touched by current work anyway, so I really see no need
to split it off.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: not available
Url : http://www.winehq.org/pipermail/wine-devel/attachments/20050511/767f6fea/attachment.pgp
More information about the wine-devel