unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefan@marxist.se>
Cc: marmot-te@riseup.net, 46236@debbugs.gnu.org, rms@gnu.org
Subject: bug#46236: 26.1; explicit the info files installation
Date: Wed, 21 Apr 2021 12:02:23 +0300	[thread overview]
Message-ID: <83fszkqacg.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkmmOKApd88xfTZaubPa4qOoWcLQOL3mhFsE_0M53GQ4_Ng@mail.gmail.com> (message from Stefan Kangas on Tue, 20 Apr 2021 22:20:03 -0500)

> From: Stefan Kangas <stefan@marxist.se>
> Date: Tue, 20 Apr 2021 22:20:03 -0500
> Cc: marmot-te <marmot-te@riseup.net>, 46236@debbugs.gnu.org
> 
> Richard Stallman <rms@gnu.org> writes:
> 
> >   > I suggest to add a notice in the info/dir file itself (or at least
> >   > an info link easy to notice, be it to the FAQ or not) that
> >   > explicit that you probably need to install system-wise :
> >   > - extra documentations packages such as bash-doc,
> >   >   emacs-common-non-dfsg (non-free repository for debian).
> >   > - ensure texinfo is installed in order to compile documentation
> >   >   when new emacs packages are installed.
> >
> > In principle this is desirable, but it may be complex.  For instance,
> > on various GNU/Linux distros the method is different.
> 
> Let's assume for the sake of argument that we only want to do this for
> Debian and derivatives.  That would require adding the non-free
> repository, thus indirectly encouraging users to use proprietary
> software.  Is that something we really would want to do?

That depend on what we say.  We don't have to mention Debian or their
repository explicitly -- which would also be better because other
distros could have a similar problem.

My problem with the suggestion is that I don't have a good idea where
to add the message.  We could:

  . display a special message when a manual is supposed to be part of
    Emacs; or
  . modify the message in case of a manual that wasn't found to better
    indicate that the user should try installing it

We could also do both.

But I don't think we should name the specific distros or their
specific package names; that way lies madness of having to maintain
those names forever.
  





  reply	other threads:[~2021-04-21  9:02 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-01 14:10 bug#46236: 26.1; explicit the info files installation marmot-te
2021-02-03  5:48 ` Richard Stallman
2021-04-21  3:20   ` Stefan Kangas
2021-04-21  9:02     ` Eli Zaretskii [this message]
2021-04-21 12:06       ` Stefan Kangas
2021-04-21 12:16         ` Eli Zaretskii
2021-04-21 12:40           ` Stefan Kangas
2021-04-21 15:32             ` Glenn Morris
2021-04-21 16:34               ` Stefan Kangas
2021-04-21 12:32         ` Gregory Heytings
2021-04-21 13:00           ` Eli Zaretskii
2021-04-21 13:47             ` Gregory Heytings
2021-04-21 13:11           ` Stefan Kangas
2021-04-21 13:54             ` Gregory Heytings
2021-04-21 14:13               ` Stefan Kangas
2021-03-06 14:25 ` Tomas Nordin
2021-03-07  6:11   ` Richard Stallman

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=83fszkqacg.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=46236@debbugs.gnu.org \
    --cc=marmot-te@riseup.net \
    --cc=rms@gnu.org \
    --cc=stefan@marxist.se \
    /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).