unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Nic Ferrier <nferrier@ferrier.me.uk>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: emacs-devel@gnu.org
Subject: Re: ELPAing all the GNU manuals
Date: Sun, 28 Sep 2014 19:17:40 +0100	[thread overview]
Message-ID: <87iok7txrv.fsf@ferrier.me.uk> (raw)
In-Reply-To: <jwvtx3rsny8.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Sun, 28 Sep 2014 12:37:26 -0400")

Stefan Monnier <monnier@IRO.UMontreal.CA> writes:

>> All GNU manuals are free. Therefore they can be redistributed.
>> All GNU manuals have texinfo (well, I'm only interested in the ones that
>> do).
>> Texinfo manuals can be turned into packages.
>> Therefore we can put all GNU texinfo manuals into ELPA.
>
> Yes, we can do that.  But just because we can doesn't mean we should.
> So what would be the benefits and the drawbacks?
>
> Clearly, you have some reason to do that.  Could you explain it to us?
>
>
>         Stefan "Preoccupied with keeping things up-to-date and in-sync"

I didn't mean to suggest it wouldn't be kept in sync. That would kind of
be the point.

The point would be to make them available to Emacs users. I am an Ubuntu
user. I just installed gnupg. No info manual appeared in my Emacs.

What I probably want is some sort of better info manual management. I
probably have the manual on my machine somewhere but it's not
automatically being found by Emacs.

I'll think more.



I shouldn't have bothered emacs-devel with a musing. But I re-assert
that is a problem. If "because we can doesn't mean we should" is a
gateway to ELPA then you've got a problem. 


Nic



  reply	other threads:[~2014-09-28 18:17 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-28  9:36 ELPAing all the GNU manuals Nic Ferrier
2014-09-28 10:47 ` Alan Mackenzie
2014-09-28 11:06   ` David Kastrup
2014-09-28 11:10     ` Nic Ferrier
2014-09-28 12:12       ` joakim
2014-09-28 12:41         ` David Kastrup
2014-09-28 12:48       ` Alan Mackenzie
2014-09-28 12:49 ` Eric Brown
2014-09-28 16:37 ` Stefan Monnier
2014-09-28 18:17   ` Nic Ferrier [this message]
2014-09-28 20:58     ` Glenn Morris
2014-09-29 10:32     ` Thomas Koch
2014-09-29 16:51       ` Nic Ferrier
2014-09-29 20:49       ` Richard Stallman
2014-09-29 12:34   ` Matthias Meulien
2014-09-29 13:25     ` Eli Zaretskii
2014-09-29 19:35       ` Matthias Meulien
2014-09-29 20:00         ` Eli Zaretskii
2014-09-29 20:47 ` 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=87iok7txrv.fsf@ferrier.me.uk \
    --to=nferrier@ferrier.me.uk \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@IRO.UMontreal.CA \
    /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).