| 1 |
On Friday 27 January 2012 16:21:21 W. Trevor King wrote: |
| 2 |
> I'm curious abotu why econf uses |
| 3 |
> |
| 4 |
> "${EPREFIX}"/var/lib |
| 5 |
|
| 6 |
my understanding is that from our sampling of packages over time, it seemed |
| 7 |
more common for upstream to expect this to be a path where they would dump |
| 8 |
state into. so if we used /var, packages would use /var/foo/ to store their |
| 9 |
crap which really belongs in /var/lib/foo/. |
| 10 |
|
| 11 |
either default is a crap one, so we went with the default that requires less |
| 12 |
ebuilds to specify --localstatedir themselves. and at this point, it's not |
| 13 |
really possible to change the behavior with EAPI, and trying to change it in a |
| 14 |
newer EAPI violates the principle of least surprise. |
| 15 |
-mike |
Archives