From: Felix Janda <felix.janda@posteo.de>
To: kbd@lists.altlinux.org
Subject: [kbd] Rename keymaps to have a unique name
Date: Sun, 9 Aug 2015 10:10:24 +0200 [thread overview]
Message-ID: <20150809081024.GA623@nyan> (raw)
Hello,
we ship several keymaps with identical names. This might lead to the
"wrong" keymap being loaded. Therefore at least Fedora[1] and Gentoo[2]
do the following renames:
mv dvorak/no.map dvorak/no-dvorak.map
mv fgGIod/trf.map fgGIod/trf-fgGIod.map
mv olpc/es.map olpc/es-olpc.map
mv olpc/pt.map olpc/pt-olpc.map
mv qwerty/cz.map qwerty/cz-qwerty.map
Here, the rename of pt.map is not strictly necessary and has only been
done for consistency. The others cover all conflicts.
I think we should rename these files but I'm not sure about some of
the new names. It would be more consistent to name the Norwegian map
dvorak-no.map. cz-qwerty.map looks good. For the rest it does not seem
to matter much whether to use a prefix or suffix.
Felix
[1]: https://bugzilla.redhat.com/show_bug.cgi?id=481674
[2]: https://bugs.gentoo.org/show_bug.cgi?id=293228
reply other threads:[~2015-08-09 8:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20150809081024.GA623@nyan \
--to=felix.janda@posteo.de \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).