| Summary: | bash blocking paludis versions (instead of the other way around) | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Mark Loeser (RETIRED) <halcy0n> |
| Component: | New packages | Assignee: | Piotr Jaroszyński (RETIRED) <peper> |
| Status: | RESOLVED INVALID | ||
| Severity: | normal | CC: | qa, spb, thermal |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Mark Loeser (RETIRED)
2008-01-14 01:03:06 UTC
Correction "block the versions of bash that it doesn't want" (In reply to comment #0) > Why have blockers been put into bash instead of paludis blocking the bash > versions that it wants? This seems to be backwards. Please make it so that > paludis blocks the versions of bash that it does not like. Because paludis enforces the dependencies of installed packages. It doesn't pick up new dependencies (or blockers) that get added in the tree. So adding it to paludis wouldn't help. Besides bash blocks portage too in exactly the same way... Given these conditions: 1) adding a blocker to an old ebuild isn't supposed to be retroactive 2) a blocker is needed because new bash should not be installed with some old package managers It seems that the simplest solution is to put the blockers in the bash ebuild. |