Large packages in the current git-based package system?
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1k
- Forks
- 1.3k
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 189
Description
Description
The current centralized one git package system seems not adapted to large packages (typically fonts, icons), typically more than 10M.
- Does it matter?
- Should large package owner push their package nevertheless?
- Is there any plan too change it?
Current maintainer of a hopefully short-lived out-of-tree package
Typst SVG Emoji
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.
Research direction
Start by reviewing the centralized git package system described in the issue and the linked Typst SVG Emoji package as a large-package example. Determine the current handling and policy for packages over 10M; done would require an agreed direction or documented guidance for package owners.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100