William Hubbs willi...@gentoo.org said:
I was told by the brltty developers that localstatedir should be /var.
I noticed, however, that econf passes --localstatedir=/var/lib to the
configure script. The way around this was to pass the --localstatedir
option to econf.
According to FHS we are
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, May 17, 2009 at 02:57:47PM -0400, Mark Loeser wrote:
According to FHS we are doing it right:
http://www.pathname.com/fhs/pub/fhs-2.3.html#VARLIBVARIABLESTATEINFORMATION
I guess what I would really like to know is...why does it matter? If
On Sunday 17 May 2009 15:55:55 William Hubbs wrote:
On Sun, May 17, 2009 at 02:57:47PM -0400, Mark Loeser wrote:
According to FHS we are doing it right:
http://www.pathname.com/fhs/pub/fhs-2.3.html#VARLIBVARIABLESTATEINFORMATI
ON
I guess what I would really like to know is...why does it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
All,
I just submitted a patch today to fix an issue with brltty and it was
partially accepted.
The part of it that wasn't accepted is what brings me to this list.
I was told by the brltty developers that localstatedir should be /var.
I noticed,
