Re: [External] : RE: org-assert-version considered harmful

[Daniel Ortmann]

    Malcolm,
    I also ran into troubles which are similar, apparently due to mixed
    org-mode versions; we've got to load org-mode before emacs tries to
    do it for us or we get mixed stuff.
    
    My resolution was to load the org-mode path first in my init.el file
    and then require org:
> (add-to-list 'load-path
>           "/home/dortmann/src/git-org-mode/lisp")
>       (require 'org)
>     
    And then I build with something like this:
> dortmann@ddo-linux:src$ cd
>         ~/src/git-org-contrib/ && git pull && cd
>         ~/src/git-org-mode/ && git pull && make all
>         && make autoloads && cd ~/src/git-emacs-master/
>         && git pull && make all && sudo -H make
>         install && cd ..
>     
    
    Then only an occasional 'make bootstrap' is required in the emacs
    build dir.

On 10/31/22 09:11, Cook, Malcolm wrote:

Hello,

 

I found this recent thread researching why my strategy for staying abreast with org head had started failing with invalid-function "org-assert-version"

 

My strategy had been to build org initially with

 

 

` cd ~/.emacs.d && git clone https://git.savannah.gnu.org/git/emacs/org-mode.git &&   cd org-mode && make autoloads && make`

 

and ensure this clone of org was picked up in my "~/.emacs.d/org-mode/lisp by including the following in my .init.el very early (right after bootstrapping the package system and use-package):

 

(use-package

  :pin manual

  :load-path "~/.emacs.d/org-mode/lisp"

)

 

Then, when I occasionally wished to update org, I would

 

`cd ~/.emacs.d/org-mode && git pull && make autoloads && make`

 

Recently I started getting errors invalid-function "org-assert-version".

 

Upon cursory reading of this thread I guessed that I could fix them by adding a `make clean` to my update mantra.

 

It worked.

 

Am I advised to do otherwise?  Is there a best/better practice?

 

Thanks,

 

~Malcolm