On 11/7/07, Nathan Middleton <[EMAIL PROTECTED]> wrote:
> On Nov 7, 2007 3:02 AM, Giambattista Bloisi <[EMAIL PROTECTED]> wrote:
> > Hi all,
> > I was just wondering whether someone in this list could give me help
> > to make a bold fix to the problem I experienced with PyGTK.
> >
> > Basically PyGTK tries to install some files into the
> > /Program/Python/2.5 UnionSandbox consider this an error and stops the
> > installation process:
> >
> > UnionSandbox: Cleaning up.
> > UnionSandbox: Moving entries to: /Programs/PyGTK/2.10.6/.SandboxInstall_Root
> > SandboxInstall: Postprocessing Sandbox
> > SandboxInstall: Left over files:
> > Programs
> > Programs/Python
> > Programs/Python/2.5
> > Programs/Python/2.5/lib
> > Programs/Python/2.5/lib/python2.5
> > Programs/Python/2.5/lib/python2.5/py_compile.pyc
> > Programs/Python/2.5/lib/python2.5/py_compile.pyo
> > Compile: Installation step failed.
> >
>
> The issue here is that during the installation the process tried to
> install files outside of the writable locations granted to the
> sandbox. The solution is to use a list of unmanaged_files. In this
> case you have two files that are "unmanaged", so adding them is fairly
> straightforward. In your recipe add something like this:
>
> unmanaged_files=(
> ${goboLibraries}/python2.5/py_compile.pyc
> ${goboLibraries}/python2.5/py_compile.pyo
> )
Um. In general, I wouldn't do that, myself... nothing should be
installing real files into /S/L except a couple of basic system
components that don't follow symlinks. The sandbox is there for a
reason. In any case, it's actually trying to install into /P/Python.
You can just remove those files pre-installation, they're not
necessary. Adding /P/P to unmanaged_files would be another stopgap of
sorts.
However, I think this is a Compile bug: those files are automatically
created when py_compile.py (the bytecode compiler) is executed;
they're a cache. The problem occurs because Python does have write
access everywhere within the sandbox, which does an end run around its
built-in sanity check. Every Python-using recipe will have to have the
same code attached to work around it.
We should either ship precompiled versions of all libraries, or teach
Compile to deal with this sensibly (assuming good behaviour all-round,
just throwing them into the appropriate /Programs entry should be
fine).
-Michael
_______________________________________________
gobolinux-devel mailing list
gobolinux-devel@lists.gobolinux.org
http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
