void-linux / void-linux/void-packages

Remove unnecessary language pack dependencies from the `libreoffice` meta package

Open
#61,257 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Shell
Stars
3.4k
Forks
2.8k
Avg merge
2d 5h
Merged PRs (30d)
299

Description

I noticed that the libreoffice meta package depends on several language packs (de, es, fr, it, pl, pt).

  • libreoffice-i18n-en-US
  • libreoffice-i18n-de
  • libreoffice-i18n-es
  • libreoffice-i18n-fr
  • libreoffice-i18n-it
  • libreoffice-i18n-pl
  • libreoffice-i18n-pt

They also pull in Hunspell, Hyphen and Mythes packages, increasing the installation size and the number of installed packages, even though most users only need a single language.

Is there a particular reason for shipping these language packs by default?
Would it make sense to make these language packs optional instead of hard dependencies?

I also wonder why these particular languages were selected while many other available language packs are not included. The current selection appears somewhat arbitrary.

Making the language packs optional would reduce unnecessary disk usage, package updates, and installed dependencies while still allowing users to install the languages they actually need.

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 locating the libreoffice meta package definition in the Void packages collection and review its current language-pack dependencies. Check the package metadata and the discussion for the reason behind the selected languages. Done means resolving whether those dependencies should remain hard requirements or become optional, with the dependency list updated accordingly.

Written by the indexing model from the issue text.

Assessment

Tech stack
shell
Domain
build-system
Issue type
Refactor
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.