Summary: | rockchip-mpp ARM64 Media Process Platform (New Package) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Viacheslav Gagara <viacheslavg> |
Component: | New packages | Assignee: | Default Assignee for New Packages <maintainer-wanted> |
Status: | UNCONFIRMED --- | ||
Severity: | enhancement | CC: | jstein |
Priority: | Normal | Keywords: | EBUILD |
Version: | unspecified | ||
Hardware: | ARM64 | ||
OS: | Linux | ||
URL: | https://github.com/rockchip-linux/mpp | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | rockchip-mpp-9999.ebuild |
Description
Viacheslav Gagara
2021-02-12 16:05:00 UTC
Created attachment 686484 [details]
rockchip-mpp-9999.ebuild
Thank you for your contribution. I had a short look on the ebuild. Here a few ideas: • Please test the ebuild with repoman full -d -x https://wiki.gentoo.org/wiki/Repoman and pkgcheck scan --net • chances to get the package in the tree are higher, if we have a package for specific version numbers, not just a live (9999) ebuild • KEYWORDS must be empty for 9999 • A bot can look for additional mistakes, if you upload a PR via github Thanks. I'm working on issues reported by repoman. Meanwhile a couple of questions: 1. What is the best/recommended approach for submitting new ebuild? I was following this guide https://wiki.gentoo.org/wiki/Submitting_ebuilds but maybe it is better to create PR directly to https://github.com/gentoo/gentoo? 2. Whom should I reference in metadata.xml as maintainer? |