| 1 |
On Sunday 17 May 2009 15:55:55 William Hubbs wrote: |
| 2 |
> On Sun, May 17, 2009 at 02:57:47PM -0400, Mark Loeser wrote: |
| 3 |
> > According to FHS we are doing it right: |
| 4 |
> > http://www.pathname.com/fhs/pub/fhs-2.3.html#VARLIBVARIABLESTATEINFORMATI |
| 5 |
> >ON |
| 6 |
> > |
| 7 |
> > I guess what I would really like to know is...why does it matter? If |
| 8 |
> > something is configurable like that, then it should work regardless of |
| 9 |
> > what is put in. |
| 10 |
> |
| 11 |
> I guess it doesn't matter to me really; I was just looking for why we do |
| 12 |
> it the way we do since one of the brltty devs "strongly recommended" |
| 13 |
> that we change our build environment. |
| 14 |
|
| 15 |
the GNU guys prefer /var which is why that is also the default. we pick |
| 16 |
/var/lib because that's how FHS works and it results in a clean /var base |
| 17 |
tree. not many packages out there will manually split things up. if your |
| 18 |
package is special and does, then using /var in your ebuild is OK, but most |
| 19 |
dont. i.e. what we're doing is correct and their strong recommendation is |
| 20 |
wrong for the default. |
| 21 |
-mike |
Archives