> > I don't think this belongs in CVS, mainly because there is no way to
> > have one authoritative spec file; every distribution needs a different
> > one. So I think it's much better to place the common stuff in a
> > separate script (like wineinstall), have a good documentation
> > explaining the various issues (like packaging.sgml), and leave it up
> > to the package developer to figure out the platform-specific details.
I have to agree with Alexandre. Packaging always has distribution specific
problems, guidelines and similar to honor, there will never be a "universal"
.spec file.
Or even "universal package names" across different packagesystems or
distributions.
(Who of you did considers SysV packages? Solaris? UnixWare?)
I don't see packaging the top of the problems why WINE is not for the
general public.
It is more like:
1. Ability to run MS Office.
This is really the Number 1 query I get and also the number 1 priority
interested WINE customers see. (Quote: "This is when I know WINE is done.")
2. Ability to run Windows Games.
A lot of home computers are currently only for:
- Internet use (Mail, Web, Chat)
- Games
The first Linux can do right now. The second not. (Heck, I would suggest
buying a DC or a PS/2, but anyway.)
As for technical issues I see:
3. General Stability
Fix all bugs. We don't want to attract instability arguments as windows
does.
4. Speed/Memory Usage.
WinWord97 on this K6-200/64MB with a bit of KDE 1 running is creating
disktraffic if I open menus. It is also way slower than in the dualbooted
Win95.
5. Implement more IPC
USER, COM currently cannot communicate over process borders. This stops
winhelp.exe from working for instance.
6. Printing
This is an unplowed field currently, which probably just needs some
attention.
Ciao, Marcus
