macaroni-os / macaroni-os/mark-issues
[eclass] Review `eclass` files, remove unused/obsolute `eclasses`, and move the rest to `kit-fixups`
- Dominant language
- No language data
- Stars
- 5
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
We've encountered a Bug caused by conflicting versions of an eclass inherited by the Qt5 ebuilds that are present in two different kits. There are also eclass files living in kits that are unused, such as the `kde.org.eclass` in `qt-kit`. The KDE ebuilds all use the `kde5.eclass` in `core-kit`.
As discussed in Discord: It seems wise to move the eclasses out of the individual kits/sources, and into `kit-fixups` at the top level, to be copied into `core-kit` by `mark-devkit`.
Contributor guide
No contributing guide indexed for this repository
Research direction
Review the eclasses in the individual kits, including qt-kit's kde.org.eclass and core-kit's kde5.eclass, and inspect the Qt5 ebuilds for conflicting inherited versions. Check how kit-fixups and mark-devkit handle eclasses. Done means unused or obsolete eclasses are removed and the remaining ones are centralized in kit-fixups for copying into core-kit.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100