HMCL-dev / HMCL-dev/HMCL

[Feature] 多个整合包相同文件使用硬链接, 而不是重新下载

Open
#4,076 0 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Java
Stars
10.1k
Forks
934
Avg merge
1d 5h
Merged PRs (30d)
82

Description

概述 | Summary

关闭版本隔离时, 不同整合包的文件会串在一起, 而开启版本隔离时, 同版本的Forge, mod, 材质包等文件仍有许多相同的, 这导致了10个同版本的整合包里有9个JEI, 剩下1个是不同版本号的JEI. 使用硬链接(hard link)代替重新下载文件, 能够显著的减少下载时间与磁盘空间

原因 | Reason

使用硬链接(hard link)代替重新下载文件, 能够显著的减少下载时间与磁盘空间

详情 | Description

使用Files.createLink创建硬链接, 对于不支持的文件系统/操作系统(非开发人员模式下的Windows), 改为复制. Windows可以提示打开开发人员模式

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing the integration-pack file download and reuse flow; the issue does not name a source file or test. Check how shared Forge, mod, and resource-pack files are currently handled, then verify that supported systems use Files.createLink while unsupported file systems and non-developer-mode Windows fall back to copying, with a Windows developer-mode prompt if applicable.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
desktop
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.