-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Offer several packages to melpa #3
Comments
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 recently started a project where I have to use jira and I, too, would like to use @nyyManni can you move |
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 <notifications@github.com> 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
|
|
@nyyManni any ideas when will |
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". |
I'm using Doom Emacs here, which transitively consumes (package! ejira :recipe
(:host github
:repo "nyyManni/ejira"
:files ("*.el")
)
) Thanks for your hard work! |
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.
The text was updated successfully, but these errors were encountered: