[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: ELPA update

From: Tassilo Horn
Subject: Re: ELPA update
Date: Wed, 28 Sep 2011 10:41:35 +0200
User-agent: Gnus/5.110018 (No Gnus v0.18) Emacs/24.0.90 (gnu/linux)

Julien Danjou <address@hidden> 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

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

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


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

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

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.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]