From: Alexey Gladkov <gladkov.alexey@gmail.com>
To: Linux console tools development discussion <kbd@lists.altlinux.org>
Subject: Re: [kbd] duplicate filenames
Date: Wed, 22 Jul 2009 00:53:00 +0400 [thread overview]
Message-ID: <4A662AAC.5030208@gmail.com> (raw)
In-Reply-To: <577f15290907181020k46499dacwd4dcdb38fe0d683@mail.gmail.com>
18.07.2009 21:20, Roman Kyrylych wrote:
> Is there any progress? At least the workaround eliminates problems
> (for example see http://bugs.archlinux.org/task/13837)
I plan it in the next major release (1.16 i think).
> We (Arch Linux) do this when building the kbd package:
> mv data/keymaps/i386/qwertz/cz{,-qwertz}.map
> mv data/keymaps/i386/olpc/es{,-olpc}.map
> mv data/keymaps/i386/olpc/pt{,-olpc}.map
> mv data/keymaps/i386/dvorak/no{,-dvorak}.map
> mv data/keymaps/i386/fgGIod/trf{,-fgGIod}.map
In this case, the /fgGIod/ is absolutely useless. I think that it is
better to remove it.
--
Rgrds, legion
prev parent reply other threads:[~2009-07-21 20:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-15 18:42 [kbd] duplicate filenames Roman Kyrylych
2008-03-15 18:43 ` Roman Kyrylych
2008-03-15 21:28 ` Alexey Gladkov
2008-03-16 23:00 ` Alexey Gladkov
2009-07-18 17:20 ` Roman Kyrylych
2009-07-21 20:53 ` Alexey Gladkov [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A662AAC.5030208@gmail.com \
--to=gladkov.alexey@gmail.com \
--cc=kbd@lists.altlinux.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox