ejira
ejira copied to clipboard
Offer several packages to melpa
It seems you have plans to put your work on melpa, this is great. Would you mind creating several melpa recipes instead of just one? I would like to write some jira-related code and I only need jiralib2.
That sounds like a good idea. It would probably make sense to make helm-ejira a separate package as well.
Hello! Thanks for the wonderful package!
@DamienCassou made an interesting point. I mostly use your package because of jiralib2.el, I use it write my own Jira-related functions.
Having only jiralib2.el as a dependency seems very reasonable for me:
- I prefer it to jiralib.el in org-jira because it's much easier (no SOAP-related complexity).
- ejira itself might serve as example code.
- It makes it possible to introduce alternative jira-related packages with different UIs based on jiralib2.el.
I recently started a project where I have to use jira and I, too, would like to use jiralib2 from this repository (and probably also ejira-parser). I don't want the other dependencies (especially helm).
@nyyManni can you move jiralib2 (and maybe the parser?) in a separate git repo and package? Thanks!
This has been hanging for a while, I'll try to squeeze some evening for this.
Afaik, there is no need to split the git repository in order to offer multiple packages on melpa, though?
Henrik Nyman [email protected] writes:
Afaik, there is no need to split the git repository in order to offer multiple packages on melpa, though?
it's not necessary unless you plan to have different releases for each package.
-- Damien Cassou http://damiencassou.seasidehosting.st
"Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill
jiralib2 is now in a separate repository and available on melpa. I'll do ejira and the related packages #later.
@nyyManni any ideas when will ejira be released on Melpa?
My apologies for being slow with this. I have actually started to work on this several times alrady, but every time got interrupted by something "more important". Splitting out the parser and helm-integration into their own modules are the biggest TODOs at the moment. I will try to arrange time as there seems to be interest for this.
I'm using Doom Emacs here, which transitively consumes straight.el. I'm using this to pull in ejira until it gets published, and figured it might be helpful to others:
(package! ejira :recipe
(:host github
:repo "nyyManni/ejira"
:files ("*.el")
)
)
Thanks for your hard work!