| Summary: | Keywording binary packages in source-based distribution | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Gangræna Gorgeous <trupanka> |
| Component: | [OLD] Unspecified | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
| Status: | RESOLVED INVALID | ||
| Severity: | normal | ||
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
This is not a topic appropriate for a bug report. I suggest you discuss it on the gentoo-dev mailing list. |
Currently there are a lot of packages in gentoo's tree that are installed without warning they are BINARY. For example, app-office/upwork, many more dev-java/* with precompiled .jar files. It's not a proper behaviour for source-base Linux distribution. There was practices to create `*-bin` packages (`maven-bin`, `icedtea-bin`) or add `-binary` USE-flag (`scala`, `seabios`, `vgabios`). But many packages that are purely binary do follow neither. Reproducible: Always Expected Results: Binary ebuilds, packages with precompiles binaries must be keyword-masked (for example, with `BINARY!!!!!!!!` keyword) or featured (`allow-binaries`) or must have USE-flag with clear semantics ('binary').