1 |
On Wednesday 06 July 2011 22:54:56 Harry Putnam did opine thusly: |
2 |
> walt <w41ter@×××××.com> writes: |
3 |
> > On 07/03/2011 03:07 PM, Harry Putnam wrote: |
4 |
> >> I'm getting output from emerge -v emacs-vcs like this: |
5 |
> >> * ERROR: app-editors/emacs-vcs-24.0.9999-r1 failed (unpack |
6 |
> >> phase): * bzr.eclass: can't pull from |
7 |
> >> bzr://bzr.savannah.gnu.org/emacs/trunk/ |
8 |
> >> |
9 |
> >> I tried |
10 |
> >> |
11 |
> >> bzr branch bzr://bzr.savannah.gnu.org/emacs/trunk/ |
12 |
> >> |
13 |
> >> by hand and had no problems with it. |
14 |
> > |
15 |
> > I've never used a 9999 version that pulls from bzr, but I have |
16 |
> > used some that pull from git and (yuk) svn. The cloned repos |
17 |
> > were stored (I think) in /usr/portage/disfiles/git (or svn) -- |
18 |
> > or something similar. |
19 |
> > |
20 |
> > If you can find a bzr repo in your /usr/portage/distfiles, try |
21 |
> > deleting it. My memory is a bit fuzzy here, but you get the |
22 |
> > general idea, I hope. |
23 |
> |
24 |
> Haaa... yep, that worked .. (deleting bzr-src) |
25 |
> |
26 |
> I was suprized to learn the repo was created in |
27 |
> /usr/portage/distfiles |
28 |
> |
29 |
> I thought it would happen in /var/tmp. Well, now I know... thanks. |
30 |
|
31 |
Repo checkouts can be very very big, so you don't want to re-download |
32 |
everything every time you build a -9999 package, hence the use of |
33 |
persistent storage. |
34 |
|
35 |
Using svn as an example, the first time you emerge the package portage |
36 |
will do a checkout. On subsequent times it will do an update, saving |
37 |
huge amounts of bandwidth. |
38 |
|
39 |
|
40 |
> |
41 |
> If you happen to do an `emerge emacs-vcs' be prepared for a really |
42 |
> looonnnnggg wait on bzr. It is the absolute slowest thing going to |
43 |
> check a module out from. |
44 |
-- |
45 |
alan dot mckinnon at gmail dot com |