[Pkg-kbd-devel] Re: pkg-kbd project on Alioth to maintain kdb Debian package

[Denis Barbier]

On Thu, Dec 15, 2005 at 02:55:13AM +0200, Anton Zinoviev wrote:
> On Thu, Dec 15, 2005 at 01:02:45AM +0100, Denis Barbier wrote:
> >
> > One more question: Why do you embed data from xlibs-data and xlibs,
> > instead of Build-Depends on these packages?
> 
> The Fonts/ckb/ directory mirrors /etc/X11/xkb.  The ckb utility uses it in
> order to generate console keymaps.  This directory is not used during
> the compilation of the package, it is part of the binary package.  In
> order to remove it from console-setup the X maintainers have to create
> a small package that contains it.

This is exactly xlibs, or did I miss something?

> Currently there are two more reasons that do not allow to use directly
> the data from xlibs.  First, currently the ckb directory mirrors
> /etc/X11/xkb of XFree86 4.3 and ckbcomp is tested thoroughly only
> with this version.  For some reason it fails with some of the keyboard
> files in X.org.

Hmmm, I did try that.  Some error messages were displayed because
<shortDescription> tag has been added, but AFAICT it seemed to
work anyway.  The attached patch shows how I did test that.

> Second, the /etc/X11/xkb/rules/{xfree86,xorg}.xml
> file seams to be buggy for some non-AT architectures.  Most non-AT
> architectures are very old and it seams that X Window is not very well
> tested on them.  I have to prepare a patch for this file.

Ok.

> The Fonts/locale/ directory mirrors /usr/X11R6/lib/X11/locale.  The
> files in this directory are used to generate the compose sequences for
> 8-bit encodings.  This generation is not straightforward because the
> compose sequences in X Window are much more powerfull.  The only
> reason why console-setup contains it own version of this directory is
> to make easy to compare this directory with the directory of X Window
> when a new version of X Window is released.  Then for each difference
> one should see how the program Keyboard/compose_translator behaves.

Ok, I will think more about this use case.

> P.S. I started the manual in the doc/ directory but is is far from
> complete. :-(

No problem, I already found that README.{,legacy}fonts were very interesting,
thanks for enlightening us ;)

Denis
-------------- next part --------------
Index: Keyboard/xmlreader
===================================================================
--- Keyboard/xmlreader	(r?vision 30)
+++ Keyboard/xmlreader	(copie de travail)
@@ -35,7 +35,7 @@
 
 my $parser = new XML::Parser (Style => 'Tree');
 
-my $tree = $parser->parsefile ('ckb/rules/xfree86.xml');
+my $tree = $parser->parsefile ($ARGV[0]);
 
 my %models;
 my %layouts;
Index: Keyboard/Makefile
===================================================================
--- Keyboard/Makefile	(r?vision 30)
+++ Keyboard/Makefile	(copie de travail)
@@ -37,9 +37,11 @@
 
 compose_files : $(compose_files)
 
+# XKBDIR = ckb
+XKBDIR = /etc/X11/xkb
 
-KeyboardNames.pl : xmlreader ckb/rules/xfree86.xml
-	./xmlreader >$@
+KeyboardNames.pl : xmlreader $(XKBDIR)/rules/xfree86.xml
+	./xmlreader $(XKBDIR)/rules/xfree86.xml >$@
 
 
 .PHONY: clean