| Summary: | Preconfigure q4wine: Pre filled paths to wine libs too | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Morgan Leijström <fri> |
| Component: | RPM Packages | Assignee: | Tomàs Deltell <tomasdeltell> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | Normal | CC: | pmdenielou |
| Version: | Cauldron | Keywords: | Triaged |
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | q4wine-1.0-0.r3.4.mga4.src.rpm | CVE: | |
| Status comment: | |||
|
Description
Morgan Leijström
2014-01-09 02:05:01 CET
Morgan Leijström
2014-01-09 02:32:45 CET
Summary:
Make it preconfigured: Pre filled paths to wine libs too =>
Preconfigure q4wine: Pre filled paths to wine libs too
Manuel Hiebel
2014-01-09 18:35:02 CET
Keywords:
(none) =>
Triaged q4wine configs are stored in user directories, not at the system directories. Otherwise, not all Wine users install the package provided by mageia (for example, if they are using a Wine builded by themselves with special patches , in order to run a specific application), so that in each case the default configuration may vary. While i think i understand that position, i also think mageia packages should contain suitable configurations to "just run" But q4wine doesn't store configs on system directories. Each user has to configure the aplication itself. OK, i think i am just too used that most everything just works - which is a good sign :) Status:
NEW =>
RESOLVED |