Karmic Wine Integration
This blueprint covers the coming changes needed for proper Wine integration in Karmic. A (small) new package will need to be installed by default, various changes to Gnome-App-Install and Wine itself will be required.
Blueprint information
- Status:
- Complete
- Approver:
- Martin Pitt
- Priority:
- Low
- Drafter:
- Scott Ritchie
- Direction:
- Needs approval
- Assignee:
- Scott Ritchie
- Definition:
- Superseded
- Series goal:
- Proposed for lucid
- Implementation:
-
Beta Available
- Milestone target:
- None
- Started by
- Scott Ritchie
- Completed by
- Scott Ritchie
Related branches
Related bugs
| Bug #111061: Wine uses Windows colors instead of Ubuntu colors | Triaged |
| Bug #488981: use wine-pulse for wine-packages | Opinion |
Whiteboard
BETA:
https:/
pitti, 2009-06-29: Approved. I moved work items into the whiteboard.
scott ritchie, 2009-06-24:
- All questions answered in updated spec
pitti, 2009-06-16:
- please add work items (template below) (use states TODO/DONE/
- can we have a way to not start clamav scanning each and every time? this seems somewhat overzealous and slows down startup
- how big are the new TTF packages? CD space is notoriously precious
-Less screensavers would free up space
- executable-handler is a script (preferably called wine-executable
- [migration] I'm not too worried about "hidden" foo.dat vs. FOO.DAT in ~/.wine, this already causes trouble; is ciopfs transparent, i. e. does it mount itself as ~/.wine/ over the real ~/.wine/?
- great plan!
Work items:
write icoutils MIR and get it to main: POSTPONED
package wine-support: POSTPONED
code ciopfs integration: POSTPONED
package ciopfs: DONE
package executable-handler: POSTPONED
split fonts in wine1.2 package: DONE
pitti, 2009-09-15: Looks we need to defer that, for Karmic it's getting very late
