Installer Request: Wine Import
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Active
- Domain
- desktop
Research direction
No files, tests, or entry points are identified in the issue. Start by mapping the existing installer and Wine Bottles import flow, then clarify the scope of directory, registry, user-profile, and Winetricks analysis. Done should include an agreed import workflow and feedback for the requested Wine directory details.
Written by the indexing model from the issue text.
Description
What it should do:
Ask for a directory where the user point to a Wine directory. The installer analyses the directory create a feedback about the status and try to import the Wine directory into Wine Bottles.
What - I as user assume - should be done:
- Try to detect what parts of the directory is Wine and what is installed on-top and what is user profile.
- analyze the registry and separate Wine standard registry entries and application entries and user made entries
- create a feedback about, Size, additional directories, some wine registry settings.
- show userprofile and ask which to import
Optional, what could enhance this importer but is not important:
- Propose reset of Wine Settings to default but allow user to tick settings they think are important and should be kept ( e.g. Audio settings, dll overwrite)
- analyze used WineTricks apps and report them in the feedback form.
- may propose an import without them and may reinstall them after that.
- Propose a wine version that may fit best for this case.
- allow to community to create analyze scripts to enhance import from certain old cases like PlayOnLinux, Q4wine, Lutris.
- Dominant language
- No language data
- Stars
- 111
- Forks
- 93
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 3
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from bottlesdevs/programs
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
bottlesdevs/programs#498 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
bottlesdevs/programs#490 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
bottlesdevs/programs#429 · 27 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 64/100
bottlesdevs/programs#497 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
bottlesdevs/programs#492 ·
All issues in bottlesdevs/programs
Similar issues
-
comp/desktop P3 type/bug
Difficulty 1/5 Under an hour Newbie friendliness 92/100
NousResearch/hermes-agent#118866 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#610 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Help-Wanted Package-Request
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
microsoft/winget-pkgs#438682 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Automattic/studio#4908 ·