| Summary: | gnome-base/gconf ebuilds violate setting $P policy | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | SpanKY <vapier> |
| Component: | [OLD] GNOME | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
'should not' , you can see we can. It works fine and we have never heard anyone having problems with it, but for the sake of esthetics (which i value more than anything) and policy never-to-be-broken-for-a-good-reason i added some lines to 2.3.3 to be compliant. |
you cannot set the $P variable inside of an ebuild but the following do: gnome-base/gconf/gconf-2.2.1.ebuild:P=${PN}-${PV} gnome-base/gconf/gconf-2.2.0.ebuild:P=${PN}-${PV} gnome-base/gconf/gconf-2.3.3.ebuild:P=${PN}-${PV}