Closed tarsius closed 1 year ago
Thanks for revisiting this. It's been 7 years since and this package is mostly considered "done" by me as there hasn't been many changes over the last couple years. So there's not a lot of overhead anymore.
Is merging this all that is necessary or is there some other work that needs to be done (i.e. recipe to melpa or so?)
Is merging this all that is necessary or is there some other work that needs to be done (i.e. recipe to melpa or so?)
The Melpa recipes for the packages build from this repository are written in a way so that they don't have to change when a new library is added to the repository. Therefore merging this is all that is needed (and it will only benefit users who install these packages by cloning the repository).
However, I had a quick look at the Melpa recipes and it appears that some packages aren't distributed there yet: dired-columns, dired-images, dired-list and dired-tagsistant. You might want to add those eventually, but that doesn't have to happen at the same time as merging this.
If you do add these to Melpa, please note that @riscy usually prefers one package per pull-request and that he usually only reviews one package per author per review round.
Friendly ping!
The prospect of maybe at some point also adding the remaining package to Melpa, shouldn't keep you from merging this now. The two are not really related--I just mentioned the former as something else that you might at one point do.
The packages not on MELPA are not really finished so I haven't published them yet. Very "use at your own risk" stuff.
I suggested this before (in #31). Despite your reluctance I've decided to give it another try now in the hope that this pull-request demonstrates that doing this won't necessarily result in an undue maintenance overhead. If this doesn't change your mind, that's fine too--but I had to try.