Re: ELPA update

[Tassilo Horn <tassilo@member.fsf.org>]

Julien Danjou <julien@danjou.info> writes:

>> But I'm open to arguments for simply setting it up as a cron job.
>
> I hope that the checks are done before commiting. :-) So I'd rather
> like a daily cronjob rathen than disturbing you each time I commit a
> bugfix that I want to give to users.

I second that.  Currently, I don't use GNU's ELPA but have a checkout of
the emacs elpa branch that I update and "make site" daily, and then I
add the "elpa/packages/<foo>/" dirs of the packages I'm interested into
my load-path manually.  That completely defeats the purpose of a package
manager...

Just found out: I guess, I could simply replace the entry

  ("gnu" . "http://elpa.gnu.org/packages/")

with

 ("gnu" . "/home/horn/repos/el/emacs/elpa/packages/")

in `package-archives' to always have the most current packages in
`package-list-packages'.

But as long as the people committing in the elpa branch pretend to know
what they do and nobody prooves the opposite, I'd still vote for an
automated process.  As the number of changes grows, a manual review
process won't catch all errors anyway, and then it's good to be able to
quickly commit a bugfix and know that that will hit the ELPA archive
short time later.

Bye,
Tassilo