On Tue, Jun 30, 2009 at 01:45:49AM +0400, Michael Raskin wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Marc Weber wrote:
By using aufs you can be pretty sure that everything works as well if
you're using aufs again in your profile, correct?
No. Maybe executable name were
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Marc Weber wrote:
Thanks, I got you now. So at least before union mounting all those store
paths there should be a test checking for conflicts and a big fat
warning.
This is where the problem lies. I know that if I have managed to make
some
summary:
* If this worked before I would have saved several days of work overall
* unkown wether this will work on Windows / Mac (?)
olegfink asked on irc today why we use symlinks instead of bind mounts
or plan9ish mounts (I don't know what they are yet)
Eg aufs can be used to create a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Marc Weber wrote:
_In depths description of the pygtk issue_:
The lib is imported by python in two phases:
import pygtk; pygtk.require 'version X'
The last command adds libPath/verisonX to its installation directiory.
The problem is that pygtk
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Marc Weber wrote:
By using aufs you can be pretty sure that everything works as well if
you're using aufs again in your profile, correct?
No. Maybe executable name were different but library set has non-trivial
file name conflict..
-BEGIN PGP
