| Summary: | dev-util/japi-compliance-checker keywording: it can support more arches like (arm arm64 x86) and so on. | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | ZongyuZ <zzy2529420793> | ||||
| Component: | Keywording | Assignee: | Miroslav Šulc <fordfrog> | ||||
| Status: | RESOLVED NEEDINFO | ||||||
| Severity: | normal | CC: | sam | ||||
| Priority: | Normal | ||||||
| Version: | unspecified | ||||||
| Hardware: | All | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Package list: |
dev-util/japi-compliance-checker
|
Runtime testing required: | --- | ||||
| Attachments: |
|
||||||
Does it work on these other architectures? We don't automatically take the intersection of keywords from dependencies, it has to work there. If you've used it on those arches, then we can test it and add it. |
Created attachment 650648 [details] japi-compliance-checker-2.4.ebuild dev-utils/japi-compliance-checker currently only supports KEYWORDS="amd64", but it is able to accept more keywords. The only dependencies of it is "dev-lang/perl" and "virtual/jdk", whose common keywords are ``` KEYWORDS="amd64 ~arm arm64 ppc64 ~x86 ~amd64-linux ~x86-linux ~ppc-macos ~x64-macos ~x86-macos ~sparc64-solaris ~x64-solaris" ``` So in my opinion, it can share the same keywording above. A sample ebuild is attached here.