Add a New Comment (Rich Markup)
Comment Type & Canned Response: None None > Multiple Canned Responses Fixed in development Crash with no stack trace Already fixed in newer version Fixed in stable Bad description Bad description and crash Bad stack trace Obsolete version Duplicate and not fixed Duplicate and needs more info Duplicate and fixed Need info and old
( Jump to the original submission )
Yeah, this is very low priority for me now a couple years later. I haven't really seen a lot of complaints here or users being pointed to this bug, so it may not be a problem that affects many or that many care about.
Closing as won't fix for now, but we can certainly reopen if people care about this.
@Mike: We skipped fixing this for the 5.1 release. Do we want to fix it for the 6.1 release? The longer we wait the less important this becomes as more and more distributions will have a sufficiently new enough version of Texinfo.
Okay, I'm marking it as WON'T FIX on the 5.0 bug fix list.
I think it has a large risk of disruption and breaking the build for users who currently build with --disable-docs. I would rather look at it on the default branch.
This seems like it would be nice to fix for 5.0 if it weren't too difficult.
Lowering priority but leaving open. This can be easily worked around on most systems by just installing a newer version of GNU Texinfo in /usr/local or other directory.
It would still be nice to separate the logic of being able to build docs from being able to install docs if they already exist in the source distribution.
I think the easiest way to think about this is to compare it to bison. If bison isn't found, we print a warning message to the user "we didn't find bison, you might be ok if you are building from the source distribution", and let it break at build time if a timestamp has been updated.
For the upcoming release, we are building docs for the users and including them in the tarball, but then configure is saying "you don't have the right version of Texinfo so we're not going to give you the docs we already built for you."
This is related to the changes to the manual that use the Texinfo @sortas macro.
It was agreed earlier that we will report an error at build time if the user has a version of Texinfo older than 6.1 that does not support the @sortas macro and they won't be able to build the manual. I think we're all in agreement that that is ok.
What I just realized is that this error also prevents anyone with an older Texinfo from even installing the user manual, even when they build from an official source release that already has the manual in it.
The problem is that the info files are not listed as a build target when (building) docs are disabled, but that also means they won't be installed even if the files are already present in the source tree.
This problem affects Ubuntu 14.04 (the old LTS, still widely used, texinfo 5.2), the current Flatpak runtime (texinfo 6.0).
(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)
Attach Files: Comment:
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Only project members can vote.
Please enter the title of George Orwell's famous dystopian book (it's a date):
Follow 5 latest changes.
Copyright © 2022 Free Software Foundation, Inc. Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved. The Levitating, Meditating, Flute-playing Gnu logo is a GNU GPL'ed image provided by the Nevrax Design Team. Source Code
Powered by Savane 3.9