Package Details: emacs-org-mode 9.6.6-2

Git Clone URL: https://aur.archlinux.org/emacs-org-mode.git (read-only, click to copy)
Package Base: emacs-org-mode
Description: Emacs Org Mode
Upstream URL: http://orgmode.org/
Keywords: emacs org-mode
Licenses: GPL
Submitter: tgirod
Maintainer: jdev082
Last Packager: jdev082
Votes: 106
Popularity: 0.131589
First Submitted: 2008-07-02 18:45 (UTC)
Last Updated: 2023-05-19 22:34 (UTC)

Dependencies (3)

Required by (2)

Sources (1)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 Next › Last »

cedricmc commented on 2014-08-06 01:47 (UTC)

With a fully updated system, I get: WARNING: Package contains reference to $pkgdir In fact, ``grep -R "$(pwd)/pkg" src/'' gives src/org-8.2.7b/lisp/org-version.el:(defvar org-odt-data-dir "$(pwd)/pkg/emacs-org-mode/usr/share/emacs/etc/org" src/org-8.2.7b/lisp/org-loaddefs.el:(defvar org-odt-data-dir "$(pwd)/pkg/emacs-org-mode/usr/share/emacs/etc/org" "\ Is this normal?

domanov commented on 2014-07-25 18:28 (UTC)

Well, I've always used makepkg --source to do my stuff, I missed that now there is need for .AURINFO and that mkaurball takes care of that. I found it out as I tried to upload the srcball to AUR. I then just did a "pacman -Ss mkaurball" and nothing came up. Then "packer -Ss mkaurball and it gave me "pkgbuild-introspection-git" - so I just installed that.

haawda commented on 2014-07-25 18:22 (UTC)

pkgbuild-introspection from [community] did not work?

domanov commented on 2014-07-25 10:06 (UTC)

Bumped to the "new" 8.2.7b. Also had to install pkgbuild-introspection-git from AUR to get "mkaurball". I somehow missed that. Enjoy!

ckruse commented on 2014-07-25 08:13 (UTC)

Could you do an upgrade to 8.2.7b?

kgunders commented on 2014-05-20 17:09 (UTC)

I think the version you get from melpa or orgmode.org's ELPA archive is the developement version. So if you want stable you may well be better off using the arch/aur package. AUR and pacman also provide better package management w.r.t. managing version rollbacks. Since org is Emacs built-in, once you uprade via ELPA there's no way to roll back, other than manually deleting the updated package from e.g. ~/.emacs.d/elpa/ In short, ELPA is kind of lame as a package management system. RSM is anal about license (I'm into FOSS but not a license nazi, MIT, BSD, Apache - it's all good) and dead tree copyright assignments so many .el authors don't bother with the hassle of submitting to gnu's elpa archives. So rather than elpa being authoritative source for one stop shopping, it's outdated and pretty much useless. Hence most .el authors are opting for second party repos such as MELPA & Marmalade. The main benefit of Emacs package system, as far as I can discern, is for users who don't have requisite permissions for installing packages system wide. Also, that having all your emacs extensions/tweaks under e.g. ~/.emacs.d makes them more portable for end user - just copy that dir and subdir to any machine. I'm far from emacs guru so take all of above with dose of salt. I did, however, inquire about this packaging mess on #emacs recently and it seems the gurus' eschew elpa, etc. and just manage their packages manually, most of which seem to have github repos, in an appropriate subdir under git control. This seems like a lot of work if you have lots of stuff but I guess on reason the gurus are gurus is that they live in emacs. Hope this helps some.

domanov commented on 2014-04-22 14:41 (UTC)

Bumped to the new 8.2.6. Enjoy!

donniezazen commented on 2013-11-08 15:15 (UTC)

Thanks @domanov. Great explanation.

domanov commented on 2013-11-08 15:04 (UTC)

@donnie: I personally prefer to try and keep all of the installed software on my different (arch) machines under control of pacman. At least if you need to install the packages system-wide, and not only in user's home. That's the beauty of arch: you then run "pacman|packer|yaourt -Syu" and you live happily everafter, everything gets updated in one place. For me this is a great added value since I have 4 or 5 arch machines that need to be kept in line. This may be of course different for you. The ELPA org package itself, what you would install from inside emacs, is in the end just the same, I guess, only pacman doesn't know anything about it and you probably need to update it manually (from inside emacs, or with a specific batch command or...) at every release. For me that would be just cumbersome, adding more complexity to my ecosystem. I never used ELPA, though, so here I might be wrong.

donniezazen commented on 2013-11-08 14:23 (UTC)

What do you think about "M-x package-install RET org" vs installation through this package? I am new to Emacs/Org.

« First ‹ Previous 1 2 3 4 5 6 7 8 9 Next › Last »