So after running my script to the point where the emerge command tries to work I guess that #5 below of my dependencies (virtual filesystem) is not required yet.
I've attached my script. It currently has dependencies on some
directories where I store haubi's toolbox, kito's tarballs, some
modified files I have made (${MATT} directory) and a unzipped stage1
directory. If anyone has questions fire away.
The script tries to run "emerge -av system" which currently gives the
following output:
*** You are not in the portage group. You may experience cache problems
*** due to permissions preventing the creation of the on-disk cache.
*** Please add this user to the portage group if you wish to use portage.
Invalid package name in package.provided: virtual/libc
Invalid package name in package.provided: virtual/linux-sources
Invalid package name in package.provided: virtual/os-headers
!!! Problem with sandbox binary. Disabling...
Traceback (most recent call last):
File
"/data1/portage/dec15/prefix/toolsbox-4-patchespre.20051215/i686-pc-linux-gnu/bin/emerge",
line 10, in ?
import portage
File
"/data1/portage/dec15/prefix/toolsbox-4-patchespre.20051215/i686-pc-linux-gnu/lib/portage/pym/portage.py",
line 6856, in ?
portdb=portdbapi(settings["PORTDIR"])
File
"/data1/portage/dec15/prefix/toolsbox-4-patchespre.20051215/i686-pc-linux-gnu/lib/portage/pym/portage.py",
line 4834, in __init__
self.auxdb[x] = self.auxdbmodule(portage_const.DEPCACHE_PATH, x,
filtered_auxdbkeys, gid=portage_gid)
File
"/data1/portage/dec15/prefix/toolsbox-4-patchespre.20051215/i686-pc-linux-gnu/lib/portage/pym/cache/flat_hash.py",
line 22, in __init__
self._ensure_dirs()
File
"/data1/portage/dec15/prefix/toolsbox-4-patchespre.20051215/i686-pc-linux-gnu/lib/portage/pym/cache/fs_template.py",
line 61, in _ensure_dirs
os.chown(base, -1, self._gid)
OSError: [Errno 1] Operation not permitted:
'/data1/portage/dec15/prefix/toolsbox-4-patchespre.20051215/i686-pc-linux-gnu/var/cache/edb/dep'
###########END OUTPUT###########
There's a few issues:
1. Portage group. Will most prefixed users have a portage group? I'm
assumming the answer is yes. Any debate here?
2. Invalid package name in package.provided. I need to look into
this. Any hints?
3. Sanbox binary. I think portage is looking for a sandbox executable
which is missing. Should this cause problems?
4. Python os.chown error. I'll look into this. Portage as of now has
a requirement to be run as root, which (I believe) Haubi removed, but
Kito hasn't. I don't think this should be a requirement. Debate?
I'm going to keep plowing ahead. Will keep you guys posted of progress I make.
matt
On 12/15/05, m h <[EMAIL PROTECTED]> wrote:
> Thanks everyone for there responses.
> I'm now re-working my effort into a script (hopefully this can be
> generalized so that others can use it).
>
> There are a few dependencies for the script:
> 1) Toolsbox
> 2) Prefixed portage
> 3) ebuild tree (including profile)
> 4) Settings (/etc files)
> 5) Virtual filesystem (/etc, /usr/, /var, etc that will reside under
> the PREFIX directory)
>
> I have questions with 3-5.
> Kito has an ebuild tree, which I can use for 3. But his profile is
> Darwin specific. He said I will need to make my own profile. But
> where do I get the profile to start from? I have a gentoo
> installation I can copy it from, but I'm trying to ask is where this
> is stored in svn... Wait, Kito said it wasn't stored, so how is it
> derived? I'm just trying to understand the process here.
>
> Regarding 4-5. Is it ok to just take this from a stage1? If so, then
> this will be arch specific (which is fine, I'm just noting that). Is
> 5 even necessary or will portage just add needed directories along the
> way?
>
> Will post my script later....
>
bootstrap.sh
Description: Bourne shell script
