Fork me on GitHub
#emacs
<
2019-02-04
>
theeternalpulse05:02:18

Finall yfinished phase one of my person emacs config, one downfall of going straight to evil mode, when your init starts failing and you don't know the emacs bindings to move around 🙂

theeternalpulse05:02:39

Has anyone used git subtree for keeping their emacs dependencies in order, I saw a site suggest to use that (I'm guessing as opposed to melpa stritctly)

vemv10:02:58

only git submodules... for many years, in conjunction with vanilla melpa. happy w/ it!

theeternalpulse18:02:49

what makes you choose a submodule vs just melpa, I know I've had issues with melpa getting the latest and it breaking, so I have to pin it, I'm guessing it's to ensure that stable versions don't change unless you want them to

vemv03:02:38

The best example would be CIDER. They tend to have quite some code churn between releases, so it's hard for them not to break something for someone in each release. Say I'm happy with Cider 0.16. Even if I use the pinned-packages stuff, melpa-stable, etc I'll be forced to use a later version, which today would be 0.19. AFAICT there's no way to specify a version number/identifier. Which tdlr is my reason for submodules

theeternalpulse04:02:30

i figured that was the case. wonder why melpa didn't factor in versioning

richiardiandrea05:02:04

Same here, I started with Emacs Live (git submodules) and slowly moving to borg

danielcompton21:02:23

There's an open issue for melpa stable providing old versions, but it's been open for a while, I think it's quite a lot of work to do it.

codeasone16:02:26

I just commit the /elpa folder with all it's dependencies into my dotemacs repo and used different branches to experiment with new releases (like new cider versions) in the knowledge that I can always inspect changes, and that master is always golden, irrespective of what is happening externally.