* bug#14064: info.info page has conflict with info package
@ 2013-03-27 12:20 Petr Hracek
2013-03-27 15:12 ` Petr Hracek
2013-03-27 15:39 ` Andreas Schwab
0 siblings, 2 replies; 16+ messages in thread
From: Petr Hracek @ 2013-03-27 12:20 UTC (permalink / raw)
To: 14064
Hi folks,
it seems that in version 24.3 all info pages located in emacs-24.3/info
directory
have names <info_page>.info which after installation have names
<info_page>.info.gz
After installation on target system info.info.gz page makes conflict
with package info.
https://bugzilla.redhat.com/show_bug.cgi?id=927996
In version 24.2 all info pages had names <info_page> which after
installation have names <info>.gz.
--
S pozdravem / Best regards
Petr Hracek
Red Hat Czech s.r.o.
BaseOS Core Services Brno
Email: phracek@redhat.com
Web: www.cz.redhat.com
^ permalink raw reply [flat|nested] 16+ messages in thread
* bug#14064: info.info page has conflict with info package
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-27 15:39 ` Andreas Schwab
1 sibling, 1 reply; 16+ messages in thread
From: Petr Hracek @ 2013-03-27 15:12 UTC (permalink / raw)
To: 14064
Just one note.
I have looked into rpm package which provides info.info.gz
and it is buildup from texlive srpm.
I think that either from emacs or from texlive should be removed.
I browsed both info files and they have really similar texts.
On 03/27/2013 01:20 PM, Petr Hracek wrote:
> Hi folks,
>
> it seems that in version 24.3 all info pages located in
> emacs-24.3/info directory
> have names <info_page>.info which after installation have names
> <info_page>.info.gz
> After installation on target system info.info.gz page makes conflict
> with package info.
> https://bugzilla.redhat.com/show_bug.cgi?id=927996
>
> In version 24.2 all info pages had names <info_page> which after
> installation have names <info>.gz.
>
--
S pozdravem / Best regards
Petr Hracek
Red Hat Czech s.r.o.
BaseOS Core Services Brno
Email: phracek@redhat.com
Web: www.cz.redhat.com
^ permalink raw reply [flat|nested] 16+ messages in thread
* bug#14064: info.info page has conflict with info package
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-27 15:39 ` Andreas Schwab
2013-03-28 8:16 ` Petr Hracek
1 sibling, 1 reply; 16+ messages in thread
From: Andreas Schwab @ 2013-03-27 15:39 UTC (permalink / raw)
To: Petr Hracek; +Cc: 14064
http://lists.gnu.org/archive/html/bug-texinfo/2013-03/msg00030.html
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."
^ permalink raw reply [flat|nested] 16+ messages in thread
* bug#14064: info.info page has conflict with info package
2013-03-27 15:39 ` Andreas Schwab
@ 2013-03-28 8:16 ` Petr Hracek
0 siblings, 0 replies; 16+ messages in thread
From: Petr Hracek @ 2013-03-28 8:16 UTC (permalink / raw)
To: Andreas Schwab; +Cc: 14064
Great thank you.
S pozdravem / Best regards
Petr Hracek
Red Hat Czech s.r.o.
BaseOS Core Services Brno
Email: phracek@redhat.com
Web: www.cz.redhat.com
On 03/27/2013 04:39 PM, Andreas Schwab wrote:
> http://lists.gnu.org/archive/html/bug-texinfo/2013-03/msg00030.html
>
> Andreas.
>
^ permalink raw reply [flat|nested] 16+ messages in thread
* bug#14064: info.info page has conflict with info package
2013-03-27 15:12 ` Petr Hracek
@ 2013-03-30 16:25 ` Glenn Morris
2013-03-30 17:09 ` Andreas Schwab
0 siblings, 1 reply; 16+ messages in thread
From: Glenn Morris @ 2013-03-30 16:25 UTC (permalink / raw)
To: Petr Hracek; +Cc: 14064
Petr Hracek wrote:
> Just one note.
>
> I have looked into rpm package which provides info.info.gz
> and it is buildup from texlive srpm.
>
> I think that either from emacs or from texlive should be removed.
> I browsed both info files and they have really similar texts.
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?
This issue is not new BTW, you're just noticing it now because prior to
Emacs 24.3, the Emacs version of the file was called "info" and the
Texinfo version was called "info.info". Eg on a RHEL 6.4 system I have
both:
rpm -qf /usr/share/info/info.gz
emacs-common-23.1-21.el6_2.3.x86_64
rpm -qf /usr/share/info/info.info.gz
info-4.13a-8.el6.x86_64
Since Emacs 24.3 the Emacs version is also called "info.info". Thus the
situation is actually better than it used to be, because now you don't
get two copies of the same file.
^ permalink raw reply [flat|nested] 16+ messages in thread
* bug#14064: info.info page has conflict with info package
2013-03-30 16:25 ` Glenn Morris
@ 2013-03-30 17:09 ` Andreas Schwab
2013-03-31 17:37 ` Glenn Morris
0 siblings, 1 reply; 16+ messages in thread
From: Andreas Schwab @ 2013-03-30 17:09 UTC (permalink / raw)
To: Glenn Morris; +Cc: 14064
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."
^ permalink raw reply [flat|nested] 16+ messages in thread
* bug#14064: info.info page has conflict with info package
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
0 siblings, 2 replies; 16+ messages in thread
From: Glenn Morris @ 2013-03-31 17:37 UTC (permalink / raw)
To: Andreas Schwab; +Cc: 14064
I can't think of a good solution for this.
Removing info.info from either Emacs or Texinfo is wrong IMO.
Renaming it breaks links between manuals.
Since the issue only shows up with package managers like rpm, then if
there is no way for those managers to deal with
non-identical-but-really-the-same-files, the least bad solution I can
think of is for the Emacs rpm to not install info.info (because I'm
betting that everyone using rpm-based systems and info has the texinfo
rpm installed and will get info.info from that).
^ permalink raw reply [flat|nested] 16+ messages in thread
* bug#14064: info.info page has conflict with info package
2013-03-31 17:37 ` Glenn Morris
@ 2013-03-31 17:40 ` Glenn Morris
2013-03-31 18:59 ` Eli Zaretskii
1 sibling, 0 replies; 16+ messages in thread
From: Glenn Morris @ 2013-03-31 17:40 UTC (permalink / raw)
To: Andreas Schwab; +Cc: 14064
PS it does not seem to be an issue for deb-based systems, because they
have chosen to install the Emacs info pages in /usr/share/info/emacs-24/
(not a good solution to this specific problem though).
^ permalink raw reply [flat|nested] 16+ messages in thread
* bug#14064: info.info page has conflict with info package
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
1 sibling, 1 reply; 16+ messages in thread
From: Eli Zaretskii @ 2013-03-31 18:59 UTC (permalink / raw)
To: Glenn Morris; +Cc: 14064, schwab
> From: Glenn Morris <rgm@gnu.org>
> Date: Sun, 31 Mar 2013 13:37:44 -0400
> Cc: 14064@debbugs.gnu.org
>
>
> I can't think of a good solution for this.
How about installing ours only if none is found in some DIR file along
INFOPATH?
> Removing info.info from either Emacs or Texinfo is wrong IMO.
Agreed.
^ permalink raw reply [flat|nested] 16+ messages in thread
* bug#14064: info.info page has conflict with info package
2013-03-31 18:59 ` Eli Zaretskii
@ 2013-03-31 22:34 ` Glenn Morris
2013-03-31 22:46 ` Glenn Morris
0 siblings, 1 reply; 16+ messages in thread
From: Glenn Morris @ 2013-03-31 22:34 UTC (permalink / raw)
To: Eli Zaretskii; +Cc: 14064, schwab
Eli Zaretskii wrote:
> How about installing ours only if none is found in some DIR file along
> INFOPATH?
What you really want is to not install on top of an existing
PREFIX/share/info/info.info; but when rpms are built they use an empty
build/install tree, so I don't think that would help. IMO it's an rpm
problem that only rpm can fix.
^ permalink raw reply [flat|nested] 16+ messages in thread
* bug#14064: info.info page has conflict with info package
2013-03-31 22:34 ` Glenn Morris
@ 2013-03-31 22:46 ` Glenn Morris
2013-04-01 5:35 ` Eli Zaretskii
0 siblings, 1 reply; 16+ messages in thread
From: Glenn Morris @ 2013-03-31 22:46 UTC (permalink / raw)
To: Eli Zaretskii; +Cc: 14064, schwab
> 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. 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.
^ permalink raw reply [flat|nested] 16+ messages in thread
* bug#14064: info.info page has conflict with info package
2013-03-31 22:46 ` Glenn Morris
@ 2013-04-01 5:35 ` Eli Zaretskii
2013-04-01 15:29 ` Glenn Morris
0 siblings, 1 reply; 16+ messages in thread
From: Eli Zaretskii @ 2013-04-01 5:35 UTC (permalink / raw)
To: Glenn Morris; +Cc: 14064, schwab
> 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?
^ permalink raw reply [flat|nested] 16+ messages in thread
* bug#14064: info.info page has conflict with info package
2013-04-01 5:35 ` Eli Zaretskii
@ 2013-04-01 15:29 ` Glenn Morris
2013-04-01 16:26 ` Eli Zaretskii
0 siblings, 1 reply; 16+ messages in thread
From: Glenn Morris @ 2013-04-01 15:29 UTC (permalink / raw)
To: Eli Zaretskii; +Cc: 14064
Eli Zaretskii wrote:
>> 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?
I won't explain this very well, but:
You configure+build+install once on one machine, making a binary rpm
that other people install on their machines. When they do so, they don't
run any of the Emacs Makefile pieces, the rpm just unpacks itself (like
a tar file, I guess, but smarter, registering what file gets installed
where, etc). It can choose to do various clever things at installation
time, but these things are controlled by the rpm's specification file,
not by any part of the Emacs normal installation rules.
AFAICS, there is literally nothing smart the Emacs Makefiles can do
about this issue, because they are not invoked at the relevant point.
^ permalink raw reply [flat|nested] 16+ messages in thread
* bug#14064: info.info page has conflict with info package
2013-04-01 15:29 ` Glenn Morris
@ 2013-04-01 16:26 ` Eli Zaretskii
2013-04-01 16:29 ` Glenn Morris
0 siblings, 1 reply; 16+ messages in thread
From: Eli Zaretskii @ 2013-04-01 16:26 UTC (permalink / raw)
To: Glenn Morris; +Cc: 14064
> From: Glenn Morris <rgm@gnu.org>
> Cc: 14064@debbugs.gnu.org
> Date: Mon, 01 Apr 2013 11:29:50 -0400
>
> Eli Zaretskii wrote:
>
> >> 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?
>
> I won't explain this very well, but:
>
> You configure+build+install once on one machine, making a binary rpm
> that other people install on their machines. When they do so, they don't
> run any of the Emacs Makefile pieces, the rpm just unpacks itself (like
> a tar file, I guess, but smarter, registering what file gets installed
> where, etc). It can choose to do various clever things at installation
> time, but these things are controlled by the rpm's specification file,
> not by any part of the Emacs normal installation rules.
>
> AFAICS, there is literally nothing smart the Emacs Makefiles can do
> about this issue, because they are not invoked at the relevant point.
That's true, but why do we bother about Emacs being installed from an
rpm? That's _really_ the job of whoever prepares the rpm. They have
the same problem with GDB, for example, which installs libbfd.
I thought we are talking about "make install", where we do control
things. Does it make sense to refrain from overwriting at that time?
^ permalink raw reply [flat|nested] 16+ messages in thread
* bug#14064: info.info page has conflict with info package
2013-04-01 16:26 ` Eli Zaretskii
@ 2013-04-01 16:29 ` Glenn Morris
2013-04-05 17:27 ` Glenn Morris
0 siblings, 1 reply; 16+ messages in thread
From: Glenn Morris @ 2013-04-01 16:29 UTC (permalink / raw)
To: Eli Zaretskii; +Cc: 14064
Eli Zaretskii wrote:
> That's true, but why do we bother about Emacs being installed from an
> rpm?
Because that's the only situation in which there is a real issue
(AFAICS), and is the original source of this report.
> That's _really_ the job of whoever prepares the rpm.
I agree, but they have reported it here.
> I thought we are talking about "make install", where we do control
> things. Does it make sense to refrain from overwriting at that time?
Not AFAICS. Why bother? Why is it any different to overwriting eg
emacs.info? It will just lead to a stale info.info hanging around
forever (not that it changes much).
^ permalink raw reply [flat|nested] 16+ messages in thread
* bug#14064: info.info page has conflict with info package
2013-04-01 16:29 ` Glenn Morris
@ 2013-04-05 17:27 ` Glenn Morris
0 siblings, 0 replies; 16+ messages in thread
From: Glenn Morris @ 2013-04-05 17:27 UTC (permalink / raw)
To: 14064-done
Closing this report as wontfix in Emacs because I think this an issue
for downstream packagers.
^ permalink raw reply [flat|nested] 16+ messages in thread
end of thread, other threads:[~2013-04-05 17:27 UTC | newest]
Thread overview: 16+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
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
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.