Ashish Panigrahi
paniashTrying to get into emacs package contributions and was wondering what the typical workflow is of doing that. For example, if I have package X installed and would like to make my own additions to the package to test it locally before sending a patch, how would I go ahead in doing that? As a beginner, I'm thinking something along the lines of using the `:load-path` attribute in use-package. #emacs
James Endres Howell@jameshowell Thanks! Nice to see that I was thinking along the right line. :)
tusharhero@paniash I either package vc or load it directly
@tusharhero Makes sense! I understood earlier that people would use straight.el but after package.el added support for :vc, that made straight.el redundant (atleast to me since iiuc, that's the selling feature of straight.el amongst other things).
pkal@paniash @tusharhero For the record, package-vc is a standalone extension of package, that allows the user to install and update packages from VC checkouts. Package-vc was developed to make contributing to packages easier, with commands like `package-vc-prepare-patch'. The :vc use-package keyword uses package-vc.
Björn@paniash Have you heard of Borg? It exactly makes that kind of thing easier.
https://emacsair.me/2016/05/17/assimilate-emacs-packages-as-git-submodules/
https://emacsair.me/2016/05/17/assimilate-emacs-packages-as-git-submodules/
yugaego 🌍@paniash Already described approaches are fine. I do it similarly, having sources cloned to the local '~/Sources/' (non-surprising) dir and loading a package from source when needed:
