all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Andreas Schwab <schwab@linux-m68k.org>
To: Glenn Morris <rgm@gnu.org>
Cc: 14064@debbugs.gnu.org
Subject: bug#14064: info.info page has conflict with info package
Date: Sat, 30 Mar 2013 18:09:06 +0100	[thread overview]
Message-ID: <m2mwtkddcd.fsf@igel.home> (raw)
In-Reply-To: <eczjxkzwg9.fsf@fencepost.gnu.org> (Glenn Morris's message of "Sat, 30 Mar 2013 12:25:26 -0400")

Glenn Morris <rgm@gnu.org> writes:

> They are basically exactly the same file, just provided by two packages.
> This is because both Emacs and Texinfo offer an info reader.
> Is this a problem? Surely there must be other instances of this kind of
> thing, and rpm must have a way to deal with this?

They are not identical, so you get a file conflict.  Also, the info
system does not allow two manuals with the same name.

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."





  reply	other threads:[~2013-03-30 17:09 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 [this message]
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
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=m2mwtkddcd.fsf@igel.home \
    --to=schwab@linux-m68k.org \
    --cc=14064@debbugs.gnu.org \
    --cc=rgm@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.