unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Chong Yidong <cyd@stupidchicken.com>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: Ted Zlatanov <tzz@lifelogs.com>, emacs-devel@gnu.org
Subject: Re: How does ELPA work?
Date: Sat, 05 Mar 2011 16:24:40 -0500	[thread overview]
Message-ID: <87fwr1feg7.fsf@stupidchicken.com> (raw)
In-Reply-To: <87sjv1i89t.fsf@gmx.de> (Michael Albinus's message of "Sat, 05 Mar 2011 22:09:50 +0100")

Michael Albinus <michael.albinus@gmx.de> writes:

>> Assuming the assignment is in order, either I or one of the maintainers
>> can do the deployment.
>
> I have the same question. I intend to upload debbugs.el to elpa. From
> the descriptions, I do not understand how I shall do it. Does there
> exist a small blurb for elpa contributors? This shouldn't include the
> upload procedure only, but also some instructions how to organize the
> package (files with version in theie name? directories with version in
> their name? readme? what else?)

There is a description of how to make Emacs packages in the Lisp manual,
in the "Packaging" node.  That should get you started.  Once you have
created a package file, you can test installing it with M-x
package-install-file RET.

To make it available on elpa.gnu.org, you currently have to ask someone
with access to the server to run the script that synches the bzr branch
on the server.  So email me or Ted Zlatanov.

We should make it easier for Emacs hackers to deploy a "private" copy of
the package archive.  The instructions of how to do this are not as
clear as they should be.  I will work on that this weekend.

(Thanks for your patience, and for being a guinea pig for using the
packaging system :-)



  reply	other threads:[~2011-03-05 21:24 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-02  9:30 How does ELPA work? joakim
2011-03-02 14:41 ` Ted Zlatanov
2011-03-05 21:09   ` Michael Albinus
2011-03-05 21:24     ` Chong Yidong [this message]
2011-03-06 22:05     ` Chong Yidong
2011-03-07 14:12       ` Michael Albinus
2011-03-08  0:25         ` Chong Yidong
2011-03-08  3:03           ` Stefan Monnier
2011-03-08 17:11             ` Chong Yidong
2011-03-08 13:03           ` Michael Albinus
2011-03-08 17:09             ` Chong Yidong
2011-03-08 17:56               ` Michael Albinus
2011-03-08 18:34                 ` Chong Yidong
2011-03-08 18:48                   ` Ted Zlatanov
2011-03-08 19:52                   ` Michael Albinus

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87fwr1feg7.fsf@stupidchicken.com \
    --to=cyd@stupidchicken.com \
    --cc=emacs-devel@gnu.org \
    --cc=michael.albinus@gmx.de \
    --cc=tzz@lifelogs.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).