I eventually used the procedure below with success, with bzr 1.3 latest main release, on a 768kbps connection. Step 1 is a 280MB download. Step 2 or 3 is an additional 70MB or so I believe. (Something between 50-100 anyway.) The value of doing (1) is speeding up (2) and (3), and also you have a directory tree organized for easy management of other branches and/or the trunk (which can all be obtained at reduced download costs).
1) wget 'http://bzr.notengoamigos.org/emacs.tar.gz' 2) cd branches 3) bzr get http://arch.sv.gnu.org/archives/emacs/bzr/emacs.app Note: bzr command 'get' = 'clone' .= 'checkout' This gets read-only; for read-write substitute sftp for http. Some brief comments on bzr -- I've never used a distributed VCS before so for those of you with this experience forgive the simplicity here. - You keep the entire repository on your disk, not just a version. - Correspondingly, when you commit, you do so to your local copy of the repository. - In addition to check in/out, there is a higher-level mechanism for transferring commits between local repositories. Such commits can be published (if you have control over an internet-accessible server) and/or sent over email so that others can acquire them. Hopefully we can use some of this functionality to advantage in developing emacs.app. There is some useful documentation on bzr that comes with the OS X binary download. Adrian ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ Emacs-app-dev- mailing list Emacs-app-dev-@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emacs-app-dev-
