macaroni-os / macaroni-os/mark-issues
Improve zfs integration with the upstream project
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 5
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
The current ebuild uses gentoo as vendor.
This vendor is also used to identify automatically the OS like visible here: https://github.com/openzfs/zfs/blob/master/config/zfs-build.m4#L600
So i open this issue to trace two different steps:
a) create a PR to zfs upsteam project to add macaroni vendor
b) create a /etc/macaroni/release or /etc/macaroni-release to use in the PR
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
Review the current ZFS ebuild and the upstream config/zfs-build.m4 around line 600 to understand how the vendor identifies the operating system. Then investigate adding the macaroni vendor upstream and choosing between /etc/macaroni/release and /etc/macaroni-release; done means an upstream PR is prepared and the selected release file is supported.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system, operating-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100