Closed PythonNut closed 8 years ago
I'm not sure where to put that. Maybe @milkypostman could chime in.
This repo will need a base16-pkg.el
file with the metadata. The way that MELPA builds this data is by trying to find base16.el
---which shouldn't exist in this case---and looking for the -pkg.el
file. So adding that with the appropriate format should work. I think you can just make it something like,
(define-package "base16" "1"
"Collection of themes built on combinations of 16 base colors"
nil
:url "https://github.com/mkaito/base16-emacs")
This should work I think. You can go ahead an commit it and see if MELPA is better then?
Added and pushed.
I'm not sure whether the link on MELPA auto-updates, but it's still pointing at the old URL. Maybe that needs to be fixed before meta-data shows up. cc: @milkypostman
The packages are rebuilt every few hours or so. It'll update on the next build.
On Wed, Apr 29, 2015 at 5:57 PM, Chris Hoppner notifications@github.com wrote:
I'm not sure whether the link on MELPA auto-updates, but it's still pointing at the old URL. Maybe that needs to be fixed before meta-data shows up. cc: @milkypostman https://github.com/milkypostman
— Reply to this email directly or view it on GitHub https://github.com/mkaito/base16-emacs/issues/10#issuecomment-97623269.
He's saying the repo in the recipes isn't correct right?
On Wed, Apr 29, 2015 at 17:59 PythonNut notifications@github.com wrote:
The packages are rebuilt every few hours or so. It'll update on the next build.
On Wed, Apr 29, 2015 at 5:57 PM, Chris Hoppner notifications@github.com wrote:
I'm not sure whether the link on MELPA auto-updates, but it's still pointing at the old URL. Maybe that needs to be fixed before meta-data shows up. cc: @milkypostman https://github.com/milkypostman
— Reply to this email directly or view it on GitHub <https://github.com/mkaito/base16-emacs/issues/10#issuecomment-97623269 .
— Reply to this email directly or view it on GitHub https://github.com/mkaito/base16-emacs/issues/10#issuecomment-97623431.
Yeah, the link on the MELPA page still points at https://github.com/neil477/base16-emacs.
Github placed a redirect there, and the package has, in fact, already been rebuilt with my changes.
Seems MELPA ain't picking up the pkg file, though, so I guess the recipe needs to be updated.
Oh. It's using your version but it hasn't recloned. Don't suppose you want to send a PR to MELPA? Cause I'm on mobile can't do it yet. But I could commit it. On Wed, Apr 29, 2015 at 18:04 Chris Hoppner notifications@github.com wrote:
Yeah, the link on the MELPA page still points at https://github.com/neil477/base16-emacs.
Github placed a redirect there, and the package has, in fact, already been rebuilt with my changes.
Seems MELPA ain't picking up the pkg file, though, so I guess the recipe needs to be updated.
— Reply to this email directly or view it on GitHub https://github.com/mkaito/base16-emacs/issues/10#issuecomment-97623937.
I've sent you a pull request.
I had no idea I could just do that, or I would have done it right away. The more you know.
Ok it's still not working. Let me take a look and figure out why and get back to you. On Thu, Apr 30, 2015 at 02:40 Chris Hoppner notifications@github.com wrote:
I've sent you a pull request https://github.com/milkypostman/melpa/pull/2724.
— Reply to this email directly or view it on GitHub https://github.com/mkaito/base16-emacs/issues/10#issuecomment-97721889.
Metadata is there, in package-list-packages.
Thanks :)
This probably means your package headers are incorrect. Please double check them, as this will affect the popularity of your package.