Perry E. Metzger | 1 Sep 2008 02:46
Gravatar

Re: xorg xkb map location


Tyler Retzlaff <rtr <at> omicron-persei-8.net> writes:
> Hi folks,
>
> There is an open pr 30982 a change request to store xkb maps under /var
> instead of under /usr/X11R{6,7}/lib/X11/xkb/ since we are tinkering with
> xorg I think this might be the right time to make this change.
>
> 1. Any objections to storing them under /var?

/var is never the appropriate place for config files. /etc is. So yes,
there are objections.

> 2. What path under /var would be most reasonable?

Perry
--

-- 
Perry E. Metzger		perry <at> piermont.com

Luke Mewburn | 1 Sep 2008 07:27
Picon

Re: xorg xkb map location

On Sun, Aug 31, 2008 at 02:55:47PM +0200, Bernd Ernesti wrote:
  | On Sun, Aug 31, 2008 at 09:57:16PM +1000, Tyler Retzlaff wrote:
  | > Hi folks,
  | > 
  | > There is an open pr 30982 a change request to store xkb maps under /var
  | > instead of under /usr/X11R{6,7}/lib/X11/xkb/ since we are tinkering with
  | > xorg I think this might be the right time to make this change.
  | > 
  | > 1. Any objections to storing them under /var?
  | > 2. What path under /var would be most reasonable?
  | 
  | The complete xkb directory or only the compiled directory under it?
  | 
  | The 'original' XFree86 use symlinks for a few directories (including xkb) in
  | /usr/X11R6/lib/X11 pointing them to /etc/X11
  | And then one symlink for /etc/X11/xkb/compiled to /var/db/xkb/compiled
  | 
  | IMHO there is no need to move all files into /var
  | 
  | : ls -la /usr/X11R6/lib/X11/
  |	[...]
  | lrwxr-xr-x   1 root  wheel     23 Apr 23  2006 xkb -> ../../../../etc/X11/xkb
  | 
  | > ls -la /etc/X11/xkb/
  |	[...]
  | lrwxrwxrwx   1 root  wheel      19 Nov 13  2005 compiled -> ../../../var/db/xkb

I think that this is the appropriate solution.  My NetBSD 3.1 system
has a similar set of symlinks, although I don't run an Xserver on it.

(Continue reading)

Valeriy E. Ushakov | 1 Sep 2008 12:53
Picon

Re: xorg xkb map location

On Sun, Aug 31, 2008 at 20:46:39 -0400, Perry E. Metzger wrote:

> Tyler Retzlaff <rtr <at> omicron-persei-8.net> writes:
>
> > There is an open pr 30982 a change request to store xkb maps under /var
> > instead of under /usr/X11R{6,7}/lib/X11/xkb/ since we are tinkering with
> > xorg I think this might be the right time to make this change.
> >
> > 1. Any objections to storing them under /var?
> 
> /var is never the appropriate place for config files. /etc is. So
> yes, there are objections.

What config files?  The directory in question contains scratch
compiled keymaps.

SY, Uwe
--

-- 
uwe <at> stderr.spb.ru                       |       Zu Grunde kommen
http://snark.ptc.spbu.ru/~uwe/          |       Ist zu Grunde gehen

Perry E. Metzger | 1 Sep 2008 16:56
Gravatar

Re: xorg xkb map location


"Valeriy E. Ushakov" <uwe <at> stderr.spb.ru> writes:
>> > There is an open pr 30982 a change request to store xkb maps under /var
>> > instead of under /usr/X11R{6,7}/lib/X11/xkb/ since we are tinkering with
>> > xorg I think this might be the right time to make this change.
>> >
>> > 1. Any objections to storing them under /var?
>> 
>> /var is never the appropriate place for config files. /etc is. So
>> yes, there are objections.
>
> What config files?  The directory in question contains scratch
> compiled keymaps.

Oops. I got it wrong, then. I thought the discussion was about the
keyboard map files themselves.

--

-- 
Perry E. Metzger		perry <at> piermont.com

Robert Swindells | 17 Sep 2008 14:56
Picon
Picon

Makefiles for xorg


Is there anything written down on how the reachover Makefiles should
work ?

I'm trying to build the kdrive server and can't get the Makefiles that
I have created to work, they just ignore additions to CPPFLAGS.

Robert Swindells

Tyler Retzlaff | 18 Sep 2008 02:33

Re: Makefiles for xorg

Hi Robert,

On Wed, Sep 17, 2008 at 01:56:58PM +0100, Robert Swindells wrote:
> 
> Is there anything written down on how the reachover Makefiles should
> work ?

Not really no.  It's more a copy what you see kind of affair.  There
are patterns in place for convenience archives vs modules but you have
to look for them.  depends on what you need to do.

> 
> I'm trying to build the kdrive server and can't get the Makefiles that
> I have created to work, they just ignore additions to CPPFLAGS.

could you give a bit more detail? where have you placed your makefiles how
have you hooked them into the reachover?

you probably want to add a section to
src/external/mit/xorg/server/xorg-server/Makefile.common that sets
XSERVER_KDRIVE server to yes|no. in
src/external/mit/xorg/server/xorg-server/Makefile evaluate
XSERVER_KDRIVE and manipulate SUBDIR appropriately to build your newly
added kdrive subdirs.

anyway, more info please.

--
Tyler R. Retzlaff

(Continue reading)

Perry E. Metzger | 20 Sep 2008 22:44
Gravatar

Re: Makefiles for xorg


Tyler Retzlaff <rtr <at> omicron-persei-8.net> writes:
> Hi Robert,
> On Wed, Sep 17, 2008 at 01:56:58PM +0100, Robert Swindells wrote:
>> 
>> Is there anything written down on how the reachover Makefiles should
>> work ?
>
> Not really no.  It's more a copy what you see kind of affair.  There
> are patterns in place for convenience archives vs modules but you have
> to look for them.  depends on what you need to do.

It might be nice if something analogous to the share/mk/bsd.README
file was written for this. I would mean more people could maintain the
code.

--

-- 
Perry E. Metzger		perry <at> piermont.com

Quentin Garnier | 21 Sep 2008 00:40

Re: Makefiles for xorg

On Sat, Sep 20, 2008 at 04:44:57PM -0400, Perry E. Metzger wrote:
> 
> Tyler Retzlaff <rtr <at> omicron-persei-8.net> writes:
> > Hi Robert,
> > On Wed, Sep 17, 2008 at 01:56:58PM +0100, Robert Swindells wrote:
> >> 
> >> Is there anything written down on how the reachover Makefiles should
> >> work ?
> >
> > Not really no.  It's more a copy what you see kind of affair.  There
> > are patterns in place for convenience archives vs modules but you have
> > to look for them.  depends on what you need to do.
> 
> It might be nice if something analogous to the share/mk/bsd.README
> file was written for this. I would mean more people could maintain the
> code.

I might try to write some stuff down later, but right now my priority
is to have the stuff working.  It's really not that complicate to get,
provided you have experience with other similar parts of our source
tree.

--

-- 
Quentin Garnier - cube <at> cubidou.net - cube <at> NetBSD.org
"See the look on my face from staying too long in one place
[...] every time the morning breaks I know I'm closer to falling"
KT Tunstall, Saving My Face, Drastic Fantastic, 2007.
Perry E. Metzger | 21 Sep 2008 18:24
Gravatar

Re: Makefiles for xorg


Quentin Garnier <cube <at> cubidou.net> writes:
>> It might be nice if something analogous to the share/mk/bsd.README
>> file was written for this. I would mean more people could maintain the
>> code.
>
> I might try to write some stuff down later, but right now my priority
> is to have the stuff working.  It's really not that complicate to get,
> provided you have experience with other similar parts of our source
> tree.

If you do have time later, please do write some of it down.

When things are undocumented, even if it only makes it a little bit
harder to fix things, that will often reduce the chances that people
will fix things on their own. Little barriers to understanding can
be enough to make people avoid doing stuff.

As an aside, I think one of the positive things that distinguishes BSD
and NetBSD in particular is the obsession with being thoroughly
documented. It makes it much easier for people to get up to speed
quickly.

--

-- 
Perry E. Metzger		perry <at> piermont.com

Robert Swindells | 22 Sep 2008 18:39
Picon
Picon

Re: Makefiles for xorg


Perry E. Metzger wrote:
>Quentin Garnier <cube <at> cubidou.net> writes:
>>> It might be nice if something analogous to the share/mk/bsd.README
>>> file was written for this. I would mean more people could maintain the
>>> code.
>>
>> I might try to write some stuff down later, but right now my priority
>> is to have the stuff working.  It's really not that complicate to get,
>> provided you have experience with other similar parts of our source
>> tree.

>If you do have time later, please do write some of it down.
>
>When things are undocumented, even if it only makes it a little bit
>harder to fix things, that will often reduce the chances that people
>will fix things on their own. Little barriers to understanding can
>be enough to make people avoid doing stuff.
>
>As an aside, I think one of the positive things that distinguishes BSD
>and NetBSD in particular is the obsession with being thoroughly
>documented. It makes it much easier for people to get up to speed
>quickly.

I think that what is needed is to document what can go wrong when
adding new stuff.

I was able to work out fairly quickly what I thought was needed in
the different Makefiles, I just can't get some of them to work.

(Continue reading)


Gmane