Add package.el-compatible package file.
Add package metadata.
the package name "eclim" could be confusing, since eclim is a different project. @tadfisher is there a reason not to call it emacs-eclim?
@fred-o looks good to me, what do you think?
Rename package to "emacs-eclim"
Merge branch 'master' of github.com:tadfisher/emacs-eclim
Delete eclim-pkg.el to test MELPA
OK, sorry about my Github skills... I've tested this now with the MELPA recipe and both the package name and the *-pkg.el file have to be named the same. So now the package name is "emacs-eclim" and shows up in the package list with the description in emacs-eclim-pkg.el.
Looks good, and I think this is a good idea. I have absolutely no experience with emacs package management, though :)
What do we need to do to get emacs-eclim into the repository?
I have a MELPA recipe that I can submit via a pull-request as soon as I get the go-ahead.
For Marmalade, I suggest packaging a stable version. The Marmalade standard is a single directory named emacs-eclim-(version) containing the project source, in a tarball called emacs-eclim-(version).tar.
looks good to me. I think we should merge this and submit the PR for MELPA.
Merge branch 'eclim-2.2.2-imports'
@tadfisher there are 6 commits for a 2 line change :) could you reorganize the branch to a single commit?
@fred-o feel free to hit merge.
I messed up because I was testing MELPA integration with the imports feature. I will create a topic branch and a cleaner pull-request tonight.
@tadfisher you can use the same pull request. Simply update the history and then do a force push on the branch of this PR. Github will automatically pick up the changes and updates the PR
Added a basic package definition based on @tadfisher's suggestion in …
I took the liberty of manually creating a package file with the contents suggested by @tadfisher. If everything looks okay, could you make the pull request with the MELPA recipe?