However,

those who need just to checkout a copy of web2py to work with it (e.g.
Sahana developers), should use

bzr export web2py_current lp:~mdipierro/web2py/devel

instead of

bzr get lp:~mdipierro/web2py/devel web2py_current

This will omit the .bzr directories and just produce a runnable copy
of the branch (3.9 MByte currently including demo apps).

Of course, from this copy you cannot work on the web2py branch, but
you can run it in any case.

Dominic

On Jul 15, 11:02 pm, Fran <[email protected]> wrote:
> Bumping this for attention - the packs folder is now 560 
> Mb!http://groups.google.com/group/web2py/msg/6143643210ee4a99
>
> This makes it very hard for developers from more bandwidth-contrained
> areas (such as Sahana developers).
>
> Suggestions:
> (1) Don't include the .w2p files in the repository (all the files in
> these tarballs are included anyway)
> (2) Don't rebuild the .w2p files on every commit - only rebuild those
> whose files have been modified
>
> Hopefully a quick hack to stop the repo from growing further is to
> simply delete from the repo:
> bzr remove admin.w2p
> bzr remove examples.w2p
> bzr remove welcome.w2p
> Then add files to .bzrignore & then they can be regenerated without
> affecting the repo size.
>
> Cleaning up the historical files from the packs may be harder - I
> guess it might need creating a new repo.
> To me this is well worthwhile as the current problem is so severe.
>
> I'd be tempted to do it like this:
> * Push old-repo to a different branch (e.g. lp:~mdipierro/web2py/old)
> * Create new repo with the current files in & push to the old
> location: lp:~mdipierro/web2py/devel
>
> Thanks,
> Fran.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"web2py Web Framework" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/web2py?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to