i wanted the rimsort can update in other drive :F not in drive :C
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.2k
- Forks
- 155
- Avg merge
- 16h 10m
- Merged PRs (30d)
- 59
Description
Origin of idea
like .msi installation for other locations, the msi installer for rimsort because the problem happens with updating in drive :F not drive :c with msi
Suggestion/proposed solution?
updating the msi in other drive like F: Instead of c: or e:, but update the rimsort in f:
Alternatives considered
No response
Additional context
No response
Code of Conduct
I agree to follow this project's Code of Conduct
Duplicate Issue Check
I've checked for similar issues and didn't find anything
Wiki/FAQ Check
I've checked the Wiki for a solution and didn't find a solution
Contributor guide
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.
Research direction
No files, tests, or entry points are identified in the issue. Start by reproducing the MSI update on drive F: and compare it with updates on drives C: and E:. The issue is done when RimSort can update successfully in the selected non-C: installation location.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- release
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100