emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <carsten.dominik@gmail.com>
To: Dan Davison <davison@stats.ox.ac.uk>
Cc: emacs-orgmode@gnu.org, Richard Riley <rileyrg@gmail.com>
Subject: Re: Re: [PROPOSAL] Quick and easy installation instructions
Date: Sun, 26 Sep 2010 17:01:00 +0200	[thread overview]
Message-ID: <11DCEC10-B532-4BAB-B721-3E3D4CBDCAC4@gmail.com> (raw)
In-Reply-To: <87zkv4wo9h.fsf@stats.ox.ac.uk>


On Sep 26, 2010, at 4:52 PM, Dan Davison wrote:

> Hi Richard,
>
> Richard Riley <rileyrg@gmail.com> writes:
>
>> Dan Davison <davison@stats.ox.ac.uk> writes:
>>
>>> I think that the documentation concerning installation should be  
>>> made
>>> more user-friendly. My impression is that the Org manual makes all  
>>> this
>>> sound much harder than it needs to be, and I suspect that this is an
>>> entry-barrier for new Org users. For example, the first thing users
>>> encounter in the manual section is an instruction to edit a  
>>> Makefile.
>>>
>>> I suggest we provide a "quick and easy installation" section to the
>>> manual, that shows people how to start using the latest version of
>>> Org-mode without messing about with compilation and installation (I
>>> rarely compile and have never "installed" Org-mode). It would also  
>>> be
>>> helpful to include notes on how to find your ".emacs" file.
>>>
>>> This would involve the following changes to section 1.2  
>>> Installation:
>>>
>>> 1. The first thing it should say would be along the lines of
>>>   "A reasonably recent version of Org is included in Emacs. Are you
>>>   sure you need the latest version of Org?  If not, skip to the
>>>   Activation section and start using Org!"
>>
>> I would not go that way. org moves very very quickly.
>>
>> I would have it in bold letters "we thoroughly recommend taking the
>> latest org release from git and here is how to do it (git pull with a
>> label)". Then if and when issues arise they can git pull as and  
>> when the
>> fixes arrive.
>
> I do understand why you say this, but these are supposed to be easy
> instructions; they should not involve usage of any version control
> software.
>
>> I say this because some distros (debian being the prime example)  
>> can be
>> very tardy with including latest versions.
>
> Yes, I agree. The org-latest.{zip,tgz} are what should be recommended
> (with the info caveat)

I think what we should recommend here is org.tar.gz and org.zip.  There
are the latest release, usually no more that 1 or 2 months old and  
stable.
Using the ..-latest files does carry this risk of making a beginner  
install
a bad version.  So if we go for beginners...

- Carsten

  reply	other threads:[~2010-09-26 15:01 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-26 13:33 [PROPOSAL] Quick and easy installation instructions Dan Davison
2010-09-26 13:44 ` Thomas S. Dye
2010-09-26 13:52 ` A. Ryan Reynolds
2010-09-26 14:21 ` Richard Riley
2010-09-26 14:52   ` Dan Davison
2010-09-26 15:01     ` Carsten Dominik [this message]
2010-09-26 15:02     ` Richard Riley
2010-09-26 21:00       ` Rémi Vanicat
2010-09-27  6:23         ` Richard Riley
2010-09-26 20:51     ` Adam
2010-09-26 14:51 ` John Hendy
2010-09-26 17:37 ` Achim Gratz
2010-09-26 18:22   ` Dan Davison
2010-09-26 19:27     ` Achim Gratz
2010-09-26 20:57       ` ELPA [WAS] " Dan Davison
2010-09-28 10:52         ` Scot Becker
2010-09-28 14:55           ` Jambunathan K
2010-09-28 17:48           ` ELPA Eric Schulte
2010-09-28 18:35             ` ELPA Sebastian Rose
2010-09-28 18:59             ` ELPA Achim Gratz
2010-09-28 19:09               ` ELPA Richard Riley
2010-09-28 20:43             ` ELPA Scot Becker
2010-09-27  6:26 ` [PROPOSAL] Quick and easy installation instructions Carsten Dominik
2010-09-27  9:00   ` Dan Davison
2010-09-27  9:55     ` Carsten Dominik
2010-09-27 10:50       ` Giovanni Ridolfi
2010-09-27 12:55       ` Sebastian Rose
2010-09-27 13:53         ` Dan Davison
2010-09-27 14:06           ` Sebastian Rose

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.orgmode.org/

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

  git send-email \
    --in-reply-to=11DCEC10-B532-4BAB-B721-3E3D4CBDCAC4@gmail.com \
    --to=carsten.dominik@gmail.com \
    --cc=davison@stats.ox.ac.uk \
    --cc=emacs-orgmode@gnu.org \
    --cc=rileyrg@gmail.com \
    /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/org-mode.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).