From: Chong Yidong <cyd@stupidchicken.com>
To: Jambunathan K <kjambunathan@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Packages + elpa.gnu.org
Date: Fri, 08 Oct 2010 23:55:52 -0400 [thread overview]
Message-ID: <87y6a86muv.fsf@stupidchicken.com> (raw)
In-Reply-To: <81eic0wsre.fsf@gmail.com> (Jambunathan K.'s message of "Fri, 08 Oct 2010 22:01:33 +0530")
Jambunathan K <kjambunathan@gmail.com> writes:
> 1. Who acts as a janitor for the elpa repository.
Me. Ted Zlatanov also has access. We've both been pretty busy on other
parts of Emacs lately, though, so there are a couple of packages that
are in the pipeline for uploading (including AuCTEX).
> 2. How does one upload packages - a mail drop to the maintainer, remote
> update from within emacs - scp, ftp etc etc . (Is package-x.el's
> package-upload-buffer and related configuration documented
> somewhere.)
Probably the easiest way to set this up is for someone on the org-mode
team to upload the dailies to a server somewhere on the web, giving the
tarball a deterministic name. Then, someone (probably me) will have to
set up a cron job on elpa.gnu.org to check for that tarball each day,
download it, and run `package-upload-file' to add it to the repository.
> 3. Does the package manager expect that builtin packages be versioned in
> a special way. For example, can the stable release be called 7.0.1
> while a daily snapshot be called 20101008?
The package manager uses the most recent version of a package, as
defined by `version-list-<'.
> 4. Any general guidelines on what packages would be accepted there and
> how often an update can happen. Are daily snapshots allowed.
The main requirement is for package copyrights to be FSF assigned. I
think providing dailies is fine.
next prev parent reply other threads:[~2010-10-09 3:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-08 16:31 Packages + elpa.gnu.org Jambunathan K
2010-10-09 3:55 ` Chong Yidong [this message]
2010-10-10 5:00 ` Ted Zlatanov
2010-10-10 5:05 ` Chong Yidong
2010-10-12 7:19 ` Bastien
2010-10-12 9:57 ` Jambunathan K
2010-10-12 10:15 ` Bastien
2010-10-28 7:55 ` Jambunathan K
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=87y6a86muv.fsf@stupidchicken.com \
--to=cyd@stupidchicken.com \
--cc=emacs-devel@gnu.org \
--cc=kjambunathan@gmail.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).