On Thu, Mar 09, 2017 at 11:08:16AM +, Daniel Stone wrote:
> Hi,
>
> On 9 March 2017 at 04:56, Peter Hutterer wrote:
> > On Wed, Mar 08, 2017 at 11:51:20AM -0500, Adam Jackson wrote:
> >> On Wed, 2017-03-08 at 13:45 +, Emil Velikov wrote:
> >> > Right, so I was
Hi,
On 9 March 2017 at 04:56, Peter Hutterer wrote:
> On Wed, Mar 08, 2017 at 11:51:20AM -0500, Adam Jackson wrote:
>> On Wed, 2017-03-08 at 13:45 +, Emil Velikov wrote:
>> > Right, so I was confused. The "compiled" xkb path and README.compiled
>> > are provided by
On Wed, Mar 08, 2017 at 11:51:20AM -0500, Adam Jackson wrote:
> On Wed, 2017-03-08 at 13:45 +, Emil Velikov wrote:
>
> > >
> > Right, so I was confused. The "compiled" xkb path and README.compiled
> > are provided by Xorg, but what's not obvious is - who is the user of
> > said path/files ?
On 8 March 2017 at 16:51, Adam Jackson wrote:
> On Wed, 2017-03-08 at 13:45 +, Emil Velikov wrote:
>
>> >
>> Right, so I was confused. The "compiled" xkb path and README.compiled
>> are provided by Xorg, but what's not obvious is - who is the user of
>> said path/files ?
>>
On Wed, 2017-03-08 at 13:45 +, Emil Velikov wrote:
> >
> Right, so I was confused. The "compiled" xkb path and README.compiled
> are provided by Xorg, but what's not obvious is - who is the user of
> said path/files ?
> This patch on its own does not make much sense, I'm afraid - we add a
>
On 8 March 2017 at 05:08, Peter Hutterer wrote:
> On Tue, Mar 07, 2017 at 09:31:54PM +, Emil Velikov wrote:
>> HI Adam,
>>
>> On 7 March 2017 at 17:42, Adam Jackson wrote:
>> > The X server (and everybody else, really) wants to know where to put
>>
On Tue, Mar 07, 2017 at 09:31:54PM +, Emil Velikov wrote:
> HI Adam,
>
> On 7 March 2017 at 17:42, Adam Jackson wrote:
> > The X server (and everybody else, really) wants to know where to put
> > xkbcomp's output, so xkbcomp.pc should say. This should be under
> >
HI Adam,
On 7 March 2017 at 17:42, Adam Jackson wrote:
> The X server (and everybody else, really) wants to know where to put
> xkbcomp's output, so xkbcomp.pc should say. This should be under
> localstatedir, since the output is architecture-dependent (as the note
> in
The X server (and everybody else, really) wants to know where to put
xkbcomp's output, so xkbcomp.pc should say. This should be under
localstatedir, since the output is architecture-dependent (as the note
in xserver/xkb/README.compiled suggests).
Signed-off-by: Adam Jackson
---