Re: New branch for elpa contents

[Ted Zlatanov]

On Fri, 19 Nov 2010 10:53:12 -0500 Chong Yidong <address@hidden> wrote: 

CY> Ted Zlatanov <address@hidden> writes:
>> 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?

CY> Your plan sounds good; if you want to go ahead and move the files,
CY> please go ahead.  I don't think we need etc/ or scripts/, the scripts
CY> and everything else can go into admin/ or a subdirectory of admin/.
CY> Also, we should add README and COPYING files to the top-level directory.

CY> Using a shell script for deployment makes more sense than using a
CY> Makefile.  We don't need to use an environment variable; just make it an
CY> argument for the shell script.

Sounds good.  One last question: right now we assume there's just "the
package repository" but I think we should expect multiple repositories.

Do you want to handle that by making a new branch for each repository or
by subdirectories for each?  In the former case we'll need an elpa-admin
branch (for ELLE-related scripts that don't change by repository) and
the other elpa branches will just have the packages.  The latter case
requires no extra work now, since we'll add repositories by making more
directories.  So punting the issue is the same as picking the
subdirectory option as far as I'm concerned.

Ted