Re: using use-package

[Stefan Monnier <monnier@IRO.UMontreal.CA>]

>> The core part of "Packaging" in the elpa.git world basically means:
>> - Start the package's main file with ";;; <name> --- <description>"
>> - Sprinkle a few ";;;###autoload"s.
>> - Add a "Package-Requires:" (when needed).
>> This is very straightforward and can be done from the very beginning
>> of development.
> I use use-package to load the modules in my personal configuration,
> which I don't intend to ever release or install as ELPA packages. Still,
> this is a minor use.

For those, Package-Requires is probably unneeded (tho if you have such
things in your use-package you could move them there), so the only thing
needed is the ";;; name -- desc" convention and a few ;;;###autoloads
(which you put in the file instead of putting them in your use-package
call).  Doesn't look like much of a hassle.

> Yes. I use cask (normally via the python wrapper), but elpakit is also
> an option here.

Not sure about Cask, but IIUC elpakit will generate a package-archive,
whereas we just want to turn the source tree into a valid "installed ELPA
package" without going through "make a tarball, create an
archive-contents, package-install".

I.e. all we want (to make those packages look like they were installed
via package.el) is to create/update a *-pkg.el and a *-autoloads.el
(we can add byte-compilation, but it's not indispensable).


        Stefan