Skip Menu |

This queue is for tickets about the Config-Model-Xorg CPAN distribution.

Report information
The Basics
Id: 27143
Status: open
Priority: 0/
Queue: Config-Model-Xorg

People
Owner: DDUMONT [...] cpan.org
Requestors: SREZIC [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)



Subject: Various problems (i.e. FreeBSD-related)
Hello Dominique, I found some problems with your xorg config module. First, on FreeBSD (at least version 6.x) the xorg.conf is not located in /etc/X11, but in /usr/X11/lib/X11. It also seams that there are a lot of alternative values missing. For example, in the keyboard configuration I had driver "kbd", XkbModel "loicdit", XkbLayout "de" etc., everything not included in the InputDevice schema. More things were missing in the other schemas. Regards, Slaven
For the xorg.conf location problem, you can work around it with -read_conf_dir and -write_conf_dir options. For a real solution, I'll need to infer xorg location from $Config{osname}. What's is osname value on FreeBSD ? For the other problems (which I fully acknowledge as xorg is a tremendously complex config), you can either send me patches to update the models (which is probably easier said than done ...) or send me your xorg.conf and I'll update myself the models. Cheers
Subject: Re: [rt.cpan.org #27143] Various problems (i.e. FreeBSD-related)
Date: 16 May 2007 21:12:40 +0200
To: bug-Config-Model-Xorg [...] rt.cpan.org
From: Slaven Rezic <slaven [...] rezic.de>
"Dominique_Dumont via RT" <bug-Config-Model-Xorg@rt.cpan.org> writes: Show quoted text
> <URL: http://rt.cpan.org/Ticket/Display.html?id=27143 > > > For the xorg.conf location problem, you can work around it with > -read_conf_dir and -write_conf_dir options. > > For a real solution, I'll need to infer xorg location from > $Config{osname}. What's is osname value on FreeBSD ?
It's "freebsd". My guess is that other BSD-like systems ("netbsd", "openbsd", "dragonfly", "darwin") use the same location, but I cannot confirm this. Maybe it's better to have a list of possible locations (possible with different ordering on BSD systems and other systems) and use the first existing one? Show quoted text
> > For the other problems (which I fully acknowledge as xorg is a > tremendously complex config), you can either send me patches to update > the models (which is probably easier said than done ...) or send me your > xorg.conf and I'll update myself the models. >
I think it's better to parse the information elsewhere. For instance information about available keyboard parameter might be found under lib/X11/xkb/rules/xorg. I see there references to my keyboard model ("logicdit", which is defined in $inetkbds and used in a "model" section), the layout ("de" is defined in $qwertz and used in a "layout" section) etc. Graphics drivers seem to be located in lib/modules/drivers on my system, e.g. "nv_drv.so" for "nv". I guess other missing information might be collected from elsewhere. Regards, Slaven -- Slaven Rezic - slaven <at> rezic <dot> de tkruler - Perl/Tk program for measuring screen distances http://ptktools.sourceforge.net/#tkruler
On Wed May 16 16:11:32 2007, slaven@rezic.de wrote: Show quoted text
> Maybe it's better to have a list of possible locations (possible with > different ordering on BSD systems and other systems) and use the first > existing one?
My goal is to be able to create an xorg config from scratch. So the writer (Config::Model::Xorg::Writer) needs to know where to write the xorg.conf file. Show quoted text
> I think it's better to parse the information elsewhere. For instance > information about available keyboard parameter might be found under > lib/X11/xkb/rules/xorg. I see there references to my keyboard model > ("logicdit", which is defined in $inetkbds and used in a "model" > section), the layout ("de" is defined in $qwertz and used in a > "layout" section) etc. Graphics drivers seem to be located in > lib/modules/drivers on my system, e.g. "nv_drv.so" for "nv". I guess > other missing information might be collected from elsewhere.
You mean that part of xorg model should be extracted from Xorg files ? Hmm, I had not thought about this possibility... I'll check what can be done with this. Thanks
From: DDUMONT [...] cpan.org
On Wed May 23 02:54:59 2007, DDUMONT wrote: Show quoted text
> You mean that part of xorg model should be extracted from > Xorg files ?
I've released a new version of Xorg model that: - use $Config{osname} to find the Xorg conf files location - with kdb driver - scan Xorg's lst files in Build.PL to generate keyboards model. This should fix most of the problems you mentioned. One thing left is that driver models are incomplete. I'll complete them later. Thing is, I cannot write all necessary models all by myself. I need help on this. But writing model in their current form, i.e. write them as perl data structure is not fun. So I don't think I'll get much help. So I need to create an easy way to edit configuration models. There are several alternatives: - implement an xml<->model translator, create dtd file and use xml editors - create a design specific language - create a "meta-model" so I could use the current Config::Model UI to create configuration models. The third option may be the fastest way, I'll give t a try soon. Cheers So my next task (beside enhancing config-model home page on sourceforge) is to create an easier way to edit
On Fri Jun 08 11:22:45 2007, DDUMONT wrote: Show quoted text
> So my next task (beside enhancing config-model home page on sourceforge) > is to create an easier way to edit
Ignore these last 2 lines. Sorry.
From: DDUMONT [...] cpan.org
Hello I've finally found the Build.PL problem with Module::Build 0.2808_01. You should now be able to install and experiment with Config::Model::Xorg on your system. OTOH, Xorg model is still incomplete (except for the keyboard part). All the best.