New branch for elpa contents

New branch for elpa contents

[Chong Yidong]

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

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

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

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

Re: New branch for elpa contents

[Ted Zlatanov]

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

Re: New branch for elpa contents

[Chong Yidong]

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.

Re: New branch for elpa contents

[Ted Zlatanov]

On Fri, 19 Nov 2010 10:53:12 -0500 Chong Yidong <cyd@stupidchicken.com> wrote: 

CY> Ted Zlatanov <tzz@lifelogs.com> 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

Re: New branch for elpa contents

[Chong Yidong]

Ted Zlatanov <tzz@lifelogs.com> writes:

> 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.

Let's punt...

Re: New branch for elpa contents

[Ted Zlatanov]

The elpa branch (bzr+ssh://USERNAME@bzr.savannah.gnu.org/emacs/elpa/)
now has the admin scripts sufficient for a full elpa.gnu.org build, the
HTML files (but no deployment script for them), and all the current
packages.  I added a barebones README, COPYING, and started a ChangLog.

Can you please verify if it works for you and you're happy with the
behavior?  I tested on elpa.gnu.org in a temporary directory.  Other
than requiring Emacs, bzr, wget, and curl it's pretty self-contained.

Steps:

bzr cat bzr://bzr.savannah.gnu.org/emacs/elpa/admin/package-update.sh > package-update.sh
./package-update.sh INSTALLDIR
cat INSTALLDIR/update-log

Ted