-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Christian Faulhammer wrote:
> Hi,
>
> Harley Peters <har...@thepetersclan.net>:
>> Since I did a full checkout with the EBZR_FETCH_CMD="bzr checkout"
>> it now deletes the entire previous checked out branch (to save disk
>> space ?) and proceeds to fetch the entire source again.
>> Why would I ever want to do that ? The whole point of bzr is to save
>> bandwidth not disk space. Is there a way arouund this ?
>
> You can add a modified bzr.eclass to a local overlay which will shadow
> the one from the Portage tree. This idea was born because initial
> checkouts are/were incredibly slow, so give first time users a better
> first experience and not let them wait 20 minutes (what happened with
> the Emacs repository).
>
> V-Li
I understand that the time trade-off favors lightweight checkouts, but if there
is a pre-existing full checkout then why secondguess the user and delete it? It
seems to me that the lines
elif [[ -d "${EBZR_BRANCH_DIR}"/.bzr/repository/ ]]; then
einfo "Re-fetching the branch to save space..."
rm -rf "${EBZR_BRANCH_DIR}"
bzr_initial_fetch "${EBZR_REPO_URI}" "${EBZR_BRANCH_DIR}"
should be removed. If users want to get rid of full checkouts they can easily
delete them themselves.
Marijn
- --
If you cannot read my mind, then listen to what I say.
Marijn Schouten (hkBst), Gentoo Lisp project, Gentoo ML
<http://www.gentoo.org/proj/en/lisp/>, #gentoo-{lisp,ml} on FreeNode
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkpbOMwACgkQp/VmCx0OL2yXBQCfVAGkJGkugj3nOoa2vgOn6cLj
X+YAn2LtVEZ3jsFVdAUArtuuRkJfKrp1
=HmE/
-----END PGP SIGNATURE-----
