Is it possible to identify the package version of a local copy/clone/fork of a Elpa supported existing package?
- A Elpa supported package (lets called it
package-foo) hosted on some Elpa compliant sites like GNU Elpa or MELPA has some problems. There might be several Pull Requests waiting for incorporation that have been sitting there for some time.
- Let's say I clone the Git repo of that package and do the merge of the waiting fixes, potentially with some of my own fixes, pushing this all back to my hosted repo and potentially providing that as another PR on the original
- I install this clone of
package-fooin a directory I put in my
All is fine and dandy I can use the
package-foo without any problem. It does not have a package version though.
- Now, if another package, lets say
package-barrequires version X.Y of
package-fooI run into a problem as Emacs will complain not being able to find it.
Is there a way I can identify a version to my copy of the
What does not work:
- I tried creating a
package-foo-pkgfile that I placed inside my extra directory that is in load-path (
~/.emacs.d/utils), but it is not recognized (perhaps it is placed in the load-path too late?).
Work-around that works
- I install the original
~/.emacs.d/elpadirectory so it can be recognized by Emacs.
- The modified
~/.emacs.d/elpa, so Emacs loads the modified
package-foobut is able to see the package version that is specified in the file stored inside
The disadvantage of this work-around is duplication plus the extra directory in
~/.emacs.d/elpa causing a little extra processing on Emacs startup.
The real solution to my problem would be the integration of the provided pull-request into the parent package. But I have no control over this.
Is there a way I can use to assign a package version to my copy of
package-foo that is located inside my secondary directory