1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA1 |
3 |
|
4 |
Christian Faulhammer wrote: |
5 |
> Hi, |
6 |
> |
7 |
> Harley Peters <harley@×××××××××××××.net>: |
8 |
>> Since I did a full checkout with the EBZR_FETCH_CMD="bzr checkout" |
9 |
>> it now deletes the entire previous checked out branch (to save disk |
10 |
>> space ?) and proceeds to fetch the entire source again. |
11 |
>> Why would I ever want to do that ? The whole point of bzr is to save |
12 |
>> bandwidth not disk space. Is there a way arouund this ? |
13 |
> |
14 |
> You can add a modified bzr.eclass to a local overlay which will shadow |
15 |
> the one from the Portage tree. This idea was born because initial |
16 |
> checkouts are/were incredibly slow, so give first time users a better |
17 |
> first experience and not let them wait 20 minutes (what happened with |
18 |
> the Emacs repository). |
19 |
> |
20 |
> V-Li |
21 |
|
22 |
I understand that the time trade-off favors lightweight checkouts, but if there |
23 |
is a pre-existing full checkout then why secondguess the user and delete it? It |
24 |
seems to me that the lines |
25 |
|
26 |
|
27 |
elif [[ -d "${EBZR_BRANCH_DIR}"/.bzr/repository/ ]]; then |
28 |
einfo "Re-fetching the branch to save space..." |
29 |
rm -rf "${EBZR_BRANCH_DIR}" |
30 |
bzr_initial_fetch "${EBZR_REPO_URI}" "${EBZR_BRANCH_DIR}" |
31 |
|
32 |
should be removed. If users want to get rid of full checkouts they can easily |
33 |
delete them themselves. |
34 |
|
35 |
Marijn |
36 |
|
37 |
- -- |
38 |
If you cannot read my mind, then listen to what I say. |
39 |
|
40 |
Marijn Schouten (hkBst), Gentoo Lisp project, Gentoo ML |
41 |
<http://www.gentoo.org/proj/en/lisp/>, #gentoo-{lisp,ml} on FreeNode |
42 |
-----BEGIN PGP SIGNATURE----- |
43 |
Version: GnuPG v2.0.11 (GNU/Linux) |
44 |
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org |
45 |
|
46 |
iEYEARECAAYFAkpbOMwACgkQp/VmCx0OL2yXBQCfVAGkJGkugj3nOoa2vgOn6cLj |
47 |
X+YAn2LtVEZ3jsFVdAUArtuuRkJfKrp1 |
48 |
=HmE/ |
49 |
-----END PGP SIGNATURE----- |