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 15:16:58 +0300	[thread overview]
Message-ID: <837dkvrfwl.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkm=q=TDzEMwspC2aOmC_NCdug1kXcTrmD1CFN8k+aPyqdA@mail.gmail.com> (message from Stefan Kangas on Wed, 21 Apr 2021 07:06:47 -0500)

> From: Stefan Kangas <stefan@marxist.se>
> Date: Wed, 21 Apr 2021 07:06:47 -0500
> Cc: rms@gnu.org, marmot-te@riseup.net, 46236@debbugs.gnu.org
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > 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.
> 
> I have never seen or heard of any other distribution ripping out the
> manual and distributing it separately from Emacs itself.  Do you know of
> any examples?

It doesn't matter.  I'm saying that we shouldn't name them as a matter
of principle, so as to avoid the few pitfalls you've mentioned, like
talking about non-free repositories.

> When I say `C-h r' without `emacs-common-non-dfsg' installed on my
> Debian machine, I get "Info file emacs does not exist".

We could, for example, say something like

  Info manual for Emacs was not found; consider installing it.

which would be more explicit and clear, I think.

> Perhaps we could just find where that message comes from

It comes from Info-find-file.

> IOW, I think this would be easy to do technically, but it would need us
> to recommend the "non-free" repository.

Which is why I suggest not to name them.

> I'm therefore starting to think that this should be the responsibility
> of Debian.  They should solve the problems that they have created for
> their users; such a warning should be added by *them*.  Doesn't that
> make more sense?

We could indeed decide that it's not our problem.  In fact, the
current situation is tantamount to doing just that.





  reply	other threads:[~2021-04-21 12:16 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
2021-04-21 12:06       ` Stefan Kangas
2021-04-21 12:16         ` Eli Zaretskii [this message]
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=837dkvrfwl.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).