Update lua-mode recipe

[immerrr]

There's an upcoming change that would require to accompany the source code with a Lua initializer script for the inferior shell. This is to ensure the script is redistributed accordingly.

Please note, that scripts directory is not there yet, and I'm not sure if the recipe works without it. If that's the case we can wait with merging until the scripts directory is created.

Brief summary of what the package does

lua-mode is a major mode for editing Lua files

Direct link to the package repository

https://github.com/immerrr/lua-mode

Your association with the package

I'm the maintainer.

Relevant communications with the upstream package maintainer

No package.el compatibility changes were introduced.

Checklist

Please confirm with x:

• The package is released under a GPL-Compatible Free Software License.
• I've read CONTRIBUTING.org
• I've used the latest version of package-lint to check for packaging issues, and addressed its feedback
• My elisp byte-compiles cleanly
• M-x checkdoc is happy with my docstrings
• I've built and installed the package using the instructions in CONTRIBUTING.org
• I have confirmed some of these without doing them

Looks like, lua-mode is quite far behind on the package quality side of things, but if it's OK I would prefer to fix it in a separate PR.

[tarsius]

Looks like, lua-mode is quite far behind on the package quality side of things, but if it's OK I would prefer to fix it in a separate PR.

That's reasonable but I would suggest you do the "I've built and installed the package using the instructions in CONTRIBUTING.org" step in order to answer your question "[the] scripts directory is not there yet, and I'm not sure if the recipe works without it."

[tarsius]

Err actually... we know that the build part succeeded and the recipe does not affect installation, so all good.

I am not sure what the best value for :files would be in this case though, so I won't merge.

[riscy]

@immerrr can you ping when the scripts directory is set up? Then we can verify the files you're specifying are being laid out exactly how you want.

You can refer to the recipe for auto-complete:

(auto-complete :repo "auto-complete/auto-complete" :fetcher github :files
               ("*.el" "dict"))

which creates a file tree that looks like this:

├── auto-complete-20170125.245   
   ├── auto-complete-autoloads.el
   ├── auto-complete-config.el   
   ├── auto-complete-config.elc  
   ├── auto-complete-pkg.el      
   ├── auto-complete.el          
   ├── auto-complete.elc         
   └── dict                      

...where the dict directory is full of files.

[purcell]

A better (and equivalent) :files pattern would be (:defaults "scripts"). I'll make that change and merge this.

[immerrr]

Thank you @purcell