From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tim Cross Subject: Re: org 9.2.6 and org 9.1.9 Date: Wed, 27 Nov 2019 17:42:39 +1100 Message-ID: References: <7D2A3D8D-CB71-4B0D-8839-9633BD9F9C4B@traduction-libre.org> <874kyqcuup.fsf@alphaville.usersys.redhat.com> <68782497-408D-4E97-8CA0-72B41882FB13@traduction-libre.org> <8325B7BB-3213-4C8D-9925-E6621695918D@traduction-libre.org> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="00000000000037fa0405984e4eb1" 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: Stefan Kangas Cc: Jean-Christophe Helary , Org-mode , Emacs developers List-Id: emacs-orgmode.gnu.org --00000000000037fa0405984e4eb1 Content-Type: text/plain; charset="UTF-8" But I don't think the issue is with package.el per se. You get the same problem if you try to install org-mode manually without package.el. What is really needed to fix this problem is some mechanism which will ensure all org related definitions are somehow purged from the running instance before attempting to install and compile a new version. Provided there is no org-mode functionality loaded when you install a later version with package.el, it works fine. On Wed, 27 Nov 2019 at 17:29, Stefan Kangas wrote: > Tim Cross writes: > > > I would agree that org should be a package in elpa and not bundled into > emacs core. The user can then choose which version to install (ignoring the > package dependency problem). > > I disagree with removing Org-mode from Emacs core, as I've explained > elsewhere. > > > This won't fix all the issues as anyone installing a new major version > when an existing version is already loaded will run into the same problems. > Bottom line, as org stands now, upgrading when org is already loaded is > problematic. > > It would be very unfortunate if we removed Org-mode from Emacs core > with the sole motivation to band-aid an issue with upgrading packages > in package.el. > > So I would put your above argument more bluntly: removing Org-mode > from Emacs core would be to sweep the problem under the rug. > package.el is still broken. > > Best regards, > Stefan Kangas > -- regards, Tim -- Tim Cross --00000000000037fa0405984e4eb1 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
But I don't think the issue is with package.el per se.= You get the same problem if you try to install org-mode manually without p= ackage.el. What is really needed to fix this problem is some mechanism whic= h will ensure all org related definitions are somehow purged from the runni= ng instance before attempting to install and compile a new version.=C2=A0 P= rovided there is no org-mode functionality loaded when you install a later = version with package.el, it works fine.

On Wed, 27 Nov 2019 at 17:29, S= tefan Kangas <stefan@marxist.se= > wrote:
Tim = Cross <theoph= ilusx@gmail.com> writes:

> I would agree that org should be a package in elpa and not bundled int= o emacs core. The user can then choose which version to install (ignoring t= he package dependency problem).

I disagree with removing Org-mode from Emacs core, as I've explained el= sewhere.

> This won't fix all the issues as anyone installing a new major ver= sion when an existing version is already loaded will run into the same prob= lems. Bottom line, as org stands now, upgrading when org is already loaded = is problematic.

It would be very unfortunate if we removed Org-mode from Emacs core
with the sole motivation to band-aid an issue with upgrading packages
in package.el.

So I would put your above argument more bluntly: removing Org-mode
from Emacs core would be to sweep the problem under the rug.
package.el is still broken.

Best regards,
Stefan Kangas


--
regards,

Tim=

--
Tim Cross

--00000000000037fa0405984e4eb1--