emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@altern.org>
To: Achim Gratz <Stromeko@nexgo.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: org-plus-contrib: Invalid function: org-no-popups
Date: Fri, 25 Jan 2013 09:51:05 +0100	[thread overview]
Message-ID: <871ud9ir2e.fsf@bzg.ath.cx> (raw)
In-Reply-To: <87pq0tzrk0.fsf@Rainer.invalid> (Achim Gratz's message of "Fri, 25 Jan 2013 07:48:31 +0100")

Achim Gratz <Stromeko@nexgo.de> writes:

> Bastien writes:
>> I already suggested to *not* use ELPA at all for now.
>
> I happen to think that this suggestion goes too far (if you think nobody
> should use OIrg from ELPA, then you'd need to stop making it available
> there and hopefully we already agreed that this isn't an option).  

No, we did not agreed this isn't an option.

I think this is an option.

> There
> is actually no problem with ELPA when you install Org from it before
> you've used Org (it wasn't designed to cope with any other situation).
> In most cases that means simply using a fresh Emacs instance to install
> Org from ELPA is good enough.  In those cases where Org is loaded during
> initialization (and systems doing that really shouldn't do this before
> package-initialize or else unload any features they have needed), one
> can resort to 'emacs -Q' if the package directory has not been changed
> from the defaults or '(unload-feature 'org t)' when that would be a
> concern.

How can you make sure that Org-mode has not been used before people 
want to install an updated version through GNU/Org ELPA?

I can't think of any good way.

Until someone have an idea about this, I'm very serious about removing
the possibility of installing Org through ELPA.  But as I said I won't
do this before getting a sense of what the users use and expect.

-- 
 Bastien

  reply	other threads:[~2013-01-25  8:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-23 17:42 org-plus-contrib: Invalid function: org-no-popups Moritz Ulrich
2013-01-24 14:08 ` Bastien
2013-01-24 20:42 ` Achim Gratz
2013-01-24 21:59   ` Bastien
2013-01-25  6:48     ` Achim Gratz
2013-01-25  8:51       ` Bastien [this message]
2013-01-25 10:33         ` Bastien
2013-01-25 19:59         ` Achim Gratz
2013-01-26 10:45           ` Bastien
2013-01-26 12:48             ` Achim Gratz
2013-01-26 13:11               ` Bastien

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=871ud9ir2e.fsf@bzg.ath.cx \
    --to=bzg@altern.org \
    --cc=Stromeko@nexgo.de \
    --cc=emacs-orgmode@gnu.org \
    /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).