| Summary: | [TRACKER] Portage incompatibilities with PMS | ||
|---|---|---|---|
| Product: | Portage Development | Reporter: | Julian Ospald <hasufell> |
| Component: | Core | Assignee: | Portage team <dev-portage> |
| Status: | CONFIRMED --- | ||
| Severity: | normal | CC: | pms, sam |
| Priority: | Normal | Keywords: | Tracker |
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Bug Depends on: | 486592, 563702, 563984, 588944, 703520, 814857, 908552, 174328, 196561, 224761, 267159, 270658, 287848, 355635, 376741, 523182, 538560, 540312, 579626, 582140, 629010, 689494, 691776, 692024, 713100, 753497, 806374, 875362, 905223, 906978, 920654 | ||
| Bug Blocks: | |||
|
Description
Julian Ospald
2015-10-22 14:34:20 UTC
this tracker is (purposefully?) misleading. there are two types of incompatibilities: (1) code accepted by the PMS but rejected by portage (2) code rejected by the PMS but accepted by portage (1) is important to address. nowhere in the PMS does it say that (2) is not permitted, nor should it. you could just as easily start a tracker bug for other PMs and list their extensions. (In reply to SpanKY from comment #1) > this tracker is (purposefully?) misleading. there are two types of > incompatibilities: > (1) code accepted by the PMS but rejected by portage > (2) code rejected by the PMS but accepted by portage > > (1) is important to address. nowhere in the PMS does it say that (2) is not > permitted, nor should it. you could just as easily start a tracker bug for > other PMs and list their extensions. It's not about extensions, but about the fact that the tree is not allowed to rely on such extensions, unless you want to break the very purpose of PMS. Because of that, all such input must be rejected for the tree. What the PM does outside of that scope is irrelevant, indeed. |
