Change History (7)
comment:1 by , 17 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
comment:2 by , 17 years ago
follow-up: 6 comment:3 by , 17 years ago
I was going to put 1.13 in last night, but I think some new keyboard layouts have crept in so the patch will need attention. Thanks for the report, I'll need to look at the example in the book (the keyboard and font are separate things, so I might change something).
Looked at what passes for the home site at altlinux, noticed 1.14 was out, but I had serious difficulties with it, for example it doesn't have a configure script and needs autoreconf to generate one. The new configure options also seem not to work. There is a 1.14.1wip there which seems to solve those problems, but work in progress versions don't normally belong in the book. I was going to raise a separate ticket after I'd dealt with 1.13 - for me, 1.14 isn't worth the aggravation.
follow-up: 5 comment:4 by , 17 years ago
The mailing list is at https://lists.altlinux.org/mailman/listinfo/kbd It has this to say about 1.13:
"I want to build another bugfix release. In fact, 1.13 was unfinished, but this release has been announced by Andries Brouwer."
I sent them a patch to fix make install, which is broken in 1.14 and 1.14.1wip.
- Marty Jack
comment:5 by , 17 years ago
Replying to martyj19:
The mailing list is at https://lists.altlinux.org/mailman/listinfo/kbd It has this to say about 1.13:
"I want to build another bugfix release. In fact, 1.13 was unfinished, but this release has been announced by Andries Brouwer."
I sent them a patch to fix make install, which is broken in 1.14 and 1.14.1wip.
- Marty Jack
Thanks for the pointer. Hopefully, 1.15 will be perfect.
comment:6 by , 17 years ago
Replying to ken@linuxfromscratch.org:
I was going to put 1.13 in last night, but I think some new keyboard layouts have crept in so the patch will need attention. Thanks for the report, I'll need to look at the example in the book (the keyboard and font are separate things, so I might change something).
In fact, as you say, that is a clfs issue. We don't give a Spanish example in LFS. You ought to flag it up there, otherwise it will appear in the 1.1.0 release. But first, please try lat9w-16 (which is included in 1.13), and report the results with using that in the clfs ticket. Thanks.
I'd be cautious with this version... In my last LFS/CLFS builds I integrated this package instead of the 1.12 one, and I found that the lat9-16 font was missing (as I'm in Spain and my keyboard is, naturally, spanish, I performed the configuration step present in CLFS for spanish keyboards), tried the new 1.14 version and now it works again with this font.
Frankly speaking, I don't know if it was just a error at the time of compiling the package, but my first impression (and advice) is to advance the package version and directly try 1.14 instead, IMHO.
Julio