Re: Improve access to documentation in Info format

[Richard Stallman <rms@gnu.org>]

[[[ To any NSA and FBI agents reading my email: please consider    ]]]
[[[ whether defending the US Constitution against all enemies,     ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]

  > > b. Write software to find the desired manual, fetch it, and install it
  > > on your computer.

  > That's the users package manager in almost all the cases. If not the
  > solutions mentioned by Suhail Singh are an option.

GNU/Linux systems use a variety of packaging systems.  (The one that is
most important in my view is .deb.)  We wouldn't be obliged in
principle to support them all, but in practice people would basically
have to impement them all.

Nonethelss, this might still be the best approach.

  > I wouldn't do this for ALL info manuals but only for those where are
  > no packages for.

Which manuals are you proposing to do this with?

                     For those where a conversion to Texinfo is done
  > e.g. Sphinx like for example when packaging CMake

Could you please describe step by step what gets done with CMake
documentation?  In order for this example to be clear as an example,
I need to know what happens in his example.

                                                      it easier to add the
  > info manual packaging to existing packaging.

I have to ask, "Easier for whom?"  Who would add the Info manual
to existing packages of CMake?  Would those people be interested
in adding it?

If they are interested, welcoming them to do this may be the easiest
for us.  But if we would have to do the job ourselves.  I think the
easiest way _for us_ to do this would be to make our own packages of
cmake.info.  That would not depend on someone specific to do work on it.

-- 
Dr Richard Stallman (https://stallman.org)
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)