emacs-devel
[Top][All Lists]
Advanced

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

Re: [RFC] Editing Lisp through changing indentation


From: Stefan Monnier
Subject: Re: [RFC] Editing Lisp through changing indentation
Date: Thu, 29 Aug 2013 16:04:44 -0400
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux)

> In ELPA, 'make archive'

Why do you need to run that?

> expects a package ChangeLog, even while
> existing packages don't have one.

At the time it is run, there should be one.

> Shall I commit this?

No, I'd rather get an error if the ChangeLog is somehow missing.

> After that, list-packages shows the new adjust-parens package in the
> local ELPA archive.

The way you should do it is just "make" and then point your archive to
.../elpa/packages.

> -*** Commit your changes the usual way ("bzr add", "bzr commit", etc).
> +*** Commit your changes the usual way ("git add", "git commit", etc).
> -Changes in the Bzr repository do not immediately propagate to the
> +Changes in the Git repository do not immediately propagate to the
>  user-facing archive (what users see when they do `M-x list-packages').
>  That is done by deploying the archive.
> @@ -67,7 +67,7 @@ and adds them to the archive.
>  ** To access a deployed archive
> -To access the archive via HTPP, have a symlink (say) /var/www/packages
> +To access the archive via HTTP, have a symlink (say) /var/www/packages
>  pointing to DEST/packages, and set up Emacs with

Oops, thanks.  Feel free to install these fixes.

> The ELPA README mentions having a "site" build target, but:

>   $ make site
>   make: *** No rule to make target `site'.  Stop.

> If the site target to Make is indeed gone, I'll remove wording from
> the README about it too.

Right, it should be replaced with the new steps of running just "make"
and pointing to .../elpa/packages rather than .../elpa/site.

> With no objections, I'll commit the above diffs and the attached
> adjust-parens.el file to ELPA.

Sounds good, thank you.


        Stefan



reply via email to

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