unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Björn Bidar" <bjorn.bidar@thaodan.de>
To: Richard Stallman <rms@gnu.org>
Cc: Eli Zaretskii <eliz@gnu.org>,  jb@jeremybryant.net,  emacs-devel@gnu.org
Subject: Re: Proposal:  Include C Manual from RMS in Emacs git, and/or release
Date: Tue, 03 Dec 2024 22:07:55 +0200	[thread overview]
Message-ID: <6302.26908703975$1733256507@news.gmane.org> (raw)
In-Reply-To: <E1tHxlB-000657-HE@fencepost.gnu.org> (Richard Stallman's message of "Sun, 01 Dec 2024 23:10:09 -0500")

Richard Stallman <rms@gnu.org> writes:

> [[[ 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. ]]]
>
>   > FWIW, I don't think this (IMO very useful and installed on my
>   > machines) manual belongs to Emacs.  It should be a separate manual.
>
> As a general design principle, it doesn't seem to make sense to
> include all GNU manuals in the Emacs distribution merely because they
> are useful manuals.  The idea was to relese them separately and have
> them installed separately into a combined info tree.
>
> Why is that not working?  What needs to be changed in some GNU/Linux
> distros?

The issues the others mentioned mainly the lack of acceptance of the
format and for sometime the possibility to find info manual manly due
the first problem.

Some projects switched to documentation systems which don't provide
anything but HTML or PDF such as e.g. Doxygen or those where the info
output is available but fragile and usually not enabled due problem one.

In the instance of the this specific manual it's just that it's one
specific document which isn't distributed along other software which is
unusual but also that it doesn't get much exposure I think.

The last issue is that the license make it impossible to be distributed
for some namely those which are Debian based but not solely those.

Related: I package the manual for RPM based distribution below:
https://build.opensuse.org/package/show/home:Thaodan:Documentation/c-intro-and-ref

I will submit the manual to openSUSE unless some other issue comes up.



      parent reply	other threads:[~2024-12-03 20:07 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-30 12:56 Proposal: Include C Manual from RMS in Emacs git, and/or release Jeremy Bryant
2024-11-30 13:25 ` Philip Kaludercic
2024-11-30 13:38 ` Arsen Arsenović
2024-11-30 14:12   ` Eli Zaretskii
2024-11-30 18:08     ` Arsen Arsenović
2024-11-30 20:05       ` Eli Zaretskii
2024-11-30 21:09         ` [External] : " Drew Adams
2024-12-01  6:15           ` Eli Zaretskii
2024-12-02  3:00             ` Texinfo reputation (was: Re: [External] : Re: Proposal: Include C Manual from RMS in Emacs git, and/or release) Max Nikulin
2024-12-02 12:47               ` Eli Zaretskii
2024-12-03  2:51                 ` Texinfo reputation Max Nikulin
2024-12-03 12:38                   ` Eli Zaretskii
2024-12-03 18:51               ` Dr. Arne Babenhauserheide
2024-12-01  9:53         ` Proposal: Include C Manual from RMS in Emacs git, and/or release Arsen Arsenović
2024-12-01 10:12           ` Eli Zaretskii
2024-12-01 10:54             ` Arsen Arsenović
2024-12-01 13:04         ` Johan Myréen
2024-12-04  6:09           ` Richard Stallman
2024-11-30 13:50 ` Eli Zaretskii
2024-12-01  4:02   ` Sean Whitton
2024-12-01  7:45     ` Eli Zaretskii
2024-12-01  8:36       ` Sean Whitton
2024-12-01 10:01         ` Eli Zaretskii
2024-12-01 11:13           ` Sean Whitton
2024-12-02  4:10   ` Richard Stallman
2024-12-02 12:57     ` Eli Zaretskii
2024-12-03 23:03       ` [ELPA] New package c-intro-and-ref -- was " Jeremy Bryant
2024-12-03 20:07     ` Björn Bidar [this message]

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='6302.26908703975$1733256507@news.gmane.org' \
    --to=bjorn.bidar@thaodan.de \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=jb@jeremybryant.net \
    --cc=rms@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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).