[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: ELPAing all the GNU manuals
From: |
Alan Mackenzie |
Subject: |
Re: ELPAing all the GNU manuals |
Date: |
Sun, 28 Sep 2014 12:48:47 +0000 |
User-agent: |
Mutt/1.5.21 (2010-09-15) |
Hello again, Nic.
On Sun, Sep 28, 2014 at 12:10:45PM +0100, Nic Ferrier wrote:
> David Kastrup <address@hidden> writes:
> > Alan Mackenzie <address@hidden> writes:
> >> You'll get one more non-authoritative place to obtain all these
> >> manuals, and from this place they're not going to be up to date,
> >> unless you figure out some mechanism of keeping them up to date.
> >> Keeping them up to date is going to be a lot of work.
> > Uh, I don't _want_ my info manuals to be up to date. I want them to
> > correspond to the software version I have installed. I have nothing to
> > gain from using copy&paste of some code from a manual that is not yet
> > supported by my software.
> I've just realized I am asking for permission and I should just be
> doing.
Another reason for not doing it is it might be bloating ELPA with what
it's not really for. This is what has happened at my day job, where our
source code repository has become the default place to store anything
and everything, like test results and reports on visits to suppliers.
The said repositiory has swollen to several 10s of Gigabytes.
But I don't know ELPA well enough to judge whether random manuals are
appropriate there. Doesn't "ELPA" stand for "elisp <something or
other>"?
> But here's one reason why things do go into ELPA. General negativity
> being almost always the first reaction on this list.
:-) Well, you did explicitly ask for opinions. You got some.
> Nic
--
Alan Mackenzie (Nuremberg, Germany).
Re: ELPAing all the GNU manuals, Eric Brown, 2014/09/28
Re: ELPAing all the GNU manuals, Stefan Monnier, 2014/09/28
Re: ELPAing all the GNU manuals, Matthias Meulien, 2014/09/29