1.1

On Mon, 2004-12-27 at 22:43 -0600, William Kilian wrote:
> 
> That's all I have for now. I'm going to see how much my build server can 
> get done while I get some sleep.
> 


Yeah, I have heard of this bug before. Here is the relevant code for
portage_confdir:

<code>
if self.settings.has_key("portage_confdir"):
print "Configuring /etc/portage..."

cmd("rm -rf "+self.settings["chroot_path"]+"/etc/portage","Error
zapping /etc/portage")

cmd("cp -R "+self.settings["portage_confdir"]+"
"+self.settings["chroot_path"]+"/etc/portage","Error
copying /etc/portage")
</code>

(excuse the bad formatting - email is responsible)

Right now, all that we are doing is copying the directory (if it exists)
into the chroot. There is no code to handle symlinks. What we could try
to do is symlink the target to $chroot_path/etc/portage regardless of
whether or not the target is a directory or symlink. The only concern
that I have is levels of symlinks - would a symlink to a symlink cause
problems?

Cheers,
//John
-- 
John Davis <zhen@g.o>
The Gentoo Foundation
Trustee | Release Engineering Manager | Catalyst code monkey

---
"When people learn no tools of judgement and merely follow their hopes,
the seeds of political manipulation are sown"
- Stephen Jay Gould