From: Eli Zaretskii <eliz@gnu.org>
To: Glenn Morris <rgm@gnu.org>
Cc: 14064@debbugs.gnu.org, schwab@linux-m68k.org
Subject: bug#14064: info.info page has conflict with info package
Date: Mon, 01 Apr 2013 08:35:41 +0300 [thread overview]
Message-ID: <83sj3a3j9u.fsf@gnu.org> (raw)
In-Reply-To: <x0d2uf427w.fsf@fencepost.gnu.org>
> From: Glenn Morris <rgm@gnu.org>
> Cc: 14064@debbugs.gnu.org, schwab@linux-m68k.org
> Date: Sun, 31 Mar 2013 18:46:27 -0400
>
> > Eli Zaretskii wrote:
> >
> >> How about installing ours only if none is found in some DIR file along
> >> INFOPATH?
>
> To be more explicit; the environment at the time the rpm is built may
> bear no relation to the environment in which it is installed.
By "environment", are you alluding to my suggestion to look along
INFOPATH? If so, we could search in certain standard directories,
such as /usr/local/share/info, as well.
> So AFAICS there is nothing clever the Emacs install rule can do
> here. As I said, I'd just make the rpm spec file unconditionally not
> install Emacs's info.info.
How is an rpm more clever than Emacs? What do they do that Emacs's
installation procedure cannot?
next prev parent reply other threads:[~2013-04-01 5:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-27 12:20 bug#14064: info.info page has conflict with info package Petr Hracek
2013-03-27 15:12 ` Petr Hracek
2013-03-30 16:25 ` Glenn Morris
2013-03-30 17:09 ` Andreas Schwab
2013-03-31 17:37 ` Glenn Morris
2013-03-31 17:40 ` Glenn Morris
2013-03-31 18:59 ` Eli Zaretskii
2013-03-31 22:34 ` Glenn Morris
2013-03-31 22:46 ` Glenn Morris
2013-04-01 5:35 ` Eli Zaretskii [this message]
2013-04-01 15:29 ` Glenn Morris
2013-04-01 16:26 ` Eli Zaretskii
2013-04-01 16:29 ` Glenn Morris
2013-04-05 17:27 ` Glenn Morris
2013-03-27 15:39 ` Andreas Schwab
2013-03-28 8:16 ` Petr Hracek
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=83sj3a3j9u.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=14064@debbugs.gnu.org \
--cc=rgm@gnu.org \
--cc=schwab@linux-m68k.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.