You are not logged in.
I migrated my dev box to Arch, just built emacs-git, and I'm painfully setting It up back to normal.
Prior to Arch, I used to just shove any elisp packages I required in ~/.emacs.d/elisp, regardless of how I acquired them (wget, git, copy/paste from emacswiki !), and never bothered with any site-lisp.
However, I'm starting to get used to the Arch way, and now this feels like I'd be missing out...
There are some packages in AUR already, but from the ones that I use, a lot are still missing ; and as I haven't made any pkgbuilds yet, the task seems a bit daunting.
Could anyone describe how can Arch improve elisp packages management, over the rather lo-fi method I just described.
I guess I need someone to explain to me what are the benefits from an emacs-er perspective.
cheers !
Offline
Look into using the Emacs Lisp Package Archive. It is a package management system for Emacs. Install it using the instructions on the site, type M-x package-list-packages, and you'll have a ton of packages available for automated installation. ELPA will be included in Emacs 24; it is an accepted part of the Emacs ecosystem.
Last edited by tss (2010-02-17 12:03:15)
Code is everything I thought poetry was... Clean, expressive, urgent, all-encompassing. Fourteen lines can open up to fill the available universe.
Teach Yourself Programming | Learn To Ask Questions | Fight Lost Productivity
Offline
Look into using the Emacs Lisp Package Archive. It is a package management system for Emacs. Install it using the instructions on the site, type M-x package-list-packages, and you'll have a ton of packages available for automated installation. ELPA will be included in Emacs 24; it is an accepted part of the Emacs ecosystem.
Yes indeed, but as with the AUR, there isn't everything I need there, maybe it will at some point, but meanwhile It'd be nice to have a solution that can manage a whole configuration...?
Offline
I love the fact some really nice Emacs packages are in the AUR. The latest org-mode is in there and it works great. So I think that if it isn't in the AUR, you should put it there! It's a fairly forgiving process. Just grab a similar Emacs package, look at the PKGBUILD file, and adapt for the one you want to add.
Offline
Prior to Arch, I used to just shove any elisp packages I required in ~/.emacs.d/elisp, regardless of how I acquired them (wget, git, copy/paste from emacswiki !), and never bothered with any site-lisp.
That is how I handle add-ons for many package. If files are not going into root directories, I see no need for package management.
Offline
One benefit of being in the AUR is that you spread the effort of updating across the whole community. I don't have to keep track of all the (sometimes very crufty) packages I have installed.
Offline
disturb wrote:Prior to Arch, I used to just shove any elisp packages I required in ~/.emacs.d/elisp, regardless of how I acquired them (wget, git, copy/paste from emacswiki !), and never bothered with any site-lisp.
That is how I handle add-ons for many package. If files are not going into root directories, I see no need for package management.
true, plus those addons usually require way more customization, so they are probably not well suited for the aur, but still, maybe a private pkgbuild would simplify the process...
Offline
Just found out about http://github.com/emacsmirror
2042 elisp repos and counting, should make for a great pkgbuild resource...
Offline