1 |
On Mon, 2004-12-27 at 22:43 -0600, William Kilian wrote: |
2 |
> |
3 |
> That's all I have for now. I'm going to see how much my build server can |
4 |
> get done while I get some sleep. |
5 |
> |
6 |
|
7 |
|
8 |
Yeah, I have heard of this bug before. Here is the relevant code for |
9 |
portage_confdir: |
10 |
|
11 |
<code> |
12 |
if self.settings.has_key("portage_confdir"): |
13 |
print "Configuring /etc/portage..." |
14 |
|
15 |
cmd("rm -rf "+self.settings["chroot_path"]+"/etc/portage","Error |
16 |
zapping /etc/portage") |
17 |
|
18 |
cmd("cp -R "+self.settings["portage_confdir"]+" |
19 |
"+self.settings["chroot_path"]+"/etc/portage","Error |
20 |
copying /etc/portage") |
21 |
</code> |
22 |
|
23 |
(excuse the bad formatting - email is responsible) |
24 |
|
25 |
Right now, all that we are doing is copying the directory (if it exists) |
26 |
into the chroot. There is no code to handle symlinks. What we could try |
27 |
to do is symlink the target to $chroot_path/etc/portage regardless of |
28 |
whether or not the target is a directory or symlink. The only concern |
29 |
that I have is levels of symlinks - would a symlink to a symlink cause |
30 |
problems? |
31 |
|
32 |
Cheers, |
33 |
//John |
34 |
-- |
35 |
John Davis <zhen@g.o> |
36 |
The Gentoo Foundation |
37 |
Trustee | Release Engineering Manager | Catalyst code monkey |
38 |
|
39 |
--- |
40 |
"When people learn no tools of judgement and merely follow their hopes, |
41 |
the seeds of political manipulation are sown" |
42 |
- Stephen Jay Gould |