From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stefan Kangas Subject: Re: org 9.2.6 and org 9.1.9 Date: Wed, 27 Nov 2019 07:18:48 +0100 Message-ID: References: <7D2A3D8D-CB71-4B0D-8839-9633BD9F9C4B@traduction-libre.org> <874kyqcuup.fsf@alphaville.usersys.redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Return-path: In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sender: "Emacs-devel" To: Jean-Christophe Helary Cc: Org-mode , Emacs developers List-Id: emacs-orgmode.gnu.org Jean-Christophe Helary writes: > > Yes, it is a bit of dependency hell. > > I see 2 solutions here: > > 1) org is only provided as a built-in package and updated there when necessary Even if we removed it from GNU ELPA, nothing stops unofficial packages from cropping up when users want to run the latest and greatest. Users of such packages would then report bugs when things broke, and we would be back where we started. (BTW, there already is a separate package archive on https://orgmode.org/elpa/.) > 2) org is removed from the built in packages Option 2 would be extremely unfortunate, to put it mildly. It would leave a lot of users without functionality they've come to expect and depend on to be there in the default install. GNU ELPA is not always a practical alternative (just to give one example, on servers or networks not connected to the internet). And even if we remove org-mode, who is to say that other packages won't see the same issues in the future? Should we just accept that we have to remove any package from Emacs which runs into this? IMO, let's work on fixing the underlying problems instead. Elsewhere in this thread, Stefan Monnier and others has pointed out what needs to be done: now we need to figure out how to do it. Best regards, Stefan Kangas