From: Chong Yidong <cyd@stupidchicken.com>
To: Ted Zlatanov <tzz@lifelogs.com>
Cc: emacs-devel@gnu.org
Subject: Re: New branch for elpa contents
Date: Fri, 19 Nov 2010 10:53:12 -0500 [thread overview]
Message-ID: <87vd3tia3b.fsf@stupidchicken.com> (raw)
In-Reply-To: <877hg9bdx4.fsf@lifelogs.com> (Ted Zlatanov's message of "Fri, 19 Nov 2010 08:12:23 -0600")
Ted Zlatanov <tzz@lifelogs.com> writes:
> Do you want to rename it to ELLE or make a new branch so named?
Let's stick with elpa.
> 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?
Your plan sounds good; if you want to go ahead and move the files,
please go ahead. I don't think we need etc/ or scripts/, the scripts
and everything else can go into admin/ or a subdirectory of admin/.
Also, we should add README and COPYING files to the top-level directory.
Using a shell script for deployment makes more sense than using a
Makefile. We don't need to use an environment variable; just make it an
argument for the shell script.
next prev parent reply other threads:[~2010-11-19 15:53 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
2010-11-19 15:53 ` Chong Yidong [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87vd3tia3b.fsf@stupidchicken.com \
--to=cyd@stupidchicken.com \
--cc=emacs-devel@gnu.org \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.