From: Glenn Morris <rgm@gnu.org>
To: Chong Yidong <cyd@gnu.org>
Cc: 12536@debbugs.gnu.org
Subject: bug#12536: 24.2.50; Outdated emacs22 icons in repo
Date: Mon, 01 Oct 2012 14:01:04 -0400 [thread overview]
Message-ID: <8gipauysv3.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <874nmedgko.fsf@gnu.org> (Chong Yidong's message of "Mon, 01 Oct 2012 11:19:51 +0800")
Chong Yidong wrote:
> The rest of the packaging issues discussed in this thread are Debian
> specific, and as far as I can tell it's not relevant to this list.
I think there is a (minor) Emacs issue as to how much configure's
--program-transform-name should affect. Currently it only affects the
Emacs and lib-src binaries.
http://www.gnu.org/savannah-checkouts/gnu/autoconf/manual/autoconf-2.69/html_node/Transformation-Rules.html
says:
Whether to do the transformations on documentation files (Texinfo or
man) is a tricky question; there seems to be no perfect answer, due
to the several reasons for name transforming. Documentation is not
usually particular to a specific architecture, and Texinfo files do
not conflict with system documentation. But they might conflict with
earlier versions of the same files, and man pages sometimes do
conflict with system documentation. As a compromise, it is probably
best to do name transformations on man pages but not on Texinfo
manuals.
which seems sensible to me.
I guess it must also affect the installed etc/images/icons/hicolor
files, and etc/emacs.desktop, if they are to function.
next prev parent reply other threads:[~2012-10-01 18:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-28 23:02 bug#12536: 24.2.50; Outdated emacs22 icons in repo Marcin Antczak
2012-09-28 23:48 ` Andreas Schwab
2012-09-29 0:13 ` Marcin Antczak
2012-09-29 0:46 ` Glenn Morris
2012-09-29 0:55 ` Marcin Antczak
2012-09-29 0:59 ` Glenn Morris
2012-10-01 0:31 ` Glenn Morris
2012-10-01 0:50 ` Marcin Antczak
2012-10-01 3:19 ` Chong Yidong
2012-10-01 18:01 ` Glenn Morris [this message]
2012-10-08 0:49 ` David De La Harpe Golden
2012-10-15 23:57 ` Glenn Morris
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=8gipauysv3.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=12536@debbugs.gnu.org \
--cc=cyd@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.