unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: emacs-devel@gnu.org
Subject: Re: New branch for elpa contents
Date: Fri, 19 Nov 2010 08:12:23 -0600	[thread overview]
Message-ID: <877hg9bdx4.fsf@lifelogs.com> (raw)
In-Reply-To: 87pqu2h3ml.fsf@stupidchicken.com

On Thu, 18 Nov 2010 13:45:54 -0500 Chong Yidong <cyd@stupidchicken.com> wrote: 

CY> Following the discussion on opening up the package repository for Emacs
CY> devs, I've made a new branch which you can check out with

CY>   bzr branch bzr+ssh://USERNAME@bzr.savannah.gnu.org/emacs/elpa elpa/

CY> Creating a local package repository from a checkout of this branch is
CY> not implemented yet.  Neither is the infrastructure for updating the
CY> actual contents of elpa.gnu.org by merging in from this branch.  Help
CY> welcome.

CY> (ttz: I made this a brand new repo; I didn't touch the existing
CY> elpa.gnu.org setup, which we'll keep running independently until this
CY> newer setup is working properly.)

Do you want to rename it to ELLE or make a new branch so named?

I'll take a look at copying the existing stuff over.  I think it should
be structured like this:

packages/
scripts/
admin/
html/
etc/

with the corresponding files from elpa.gnu.org inside.  Bootstrapping a
mirror should be as simple as checking it out and running
scripts/deploy.sh or "make deploy" or something like that, based on a
single environment variable ELPA_DEPLOY_ROOT.  That would let us deploy
a copy as part of the Emacs build process if we or users choose to, or
let distros or third parties package such deployments.

Would you rather do it my way or put just the packages in the branch?

Ted




  reply	other threads:[~2010-11-19 14:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-18 18:45 New branch for elpa contents Chong Yidong
2010-11-19 14:12 ` Ted Zlatanov [this message]
2010-11-19 15:53   ` Chong Yidong
2010-11-19 16:17     ` Ted Zlatanov
2010-11-19 16:43       ` Chong Yidong
2010-11-20 17:36         ` Ted Zlatanov

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=877hg9bdx4.fsf@lifelogs.com \
    --to=tzz@lifelogs.com \
    --cc=emacs-devel@gnu.org \
    /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).