Here is a sample scenario :
Start from a new directory say /myapps . Install a separate (pre-compiled or source) python to say ./usr/bin (relative to installation directory and not system /usr/bin) and install various eggs to this custom python . This can be done using perhaps something like buildout .
Now another user having the same OS version just rsync's the folder maitaining the exact folder structure, will he be able to use python just like the other user . Does he have to really install stuff again ?
I thought most of the Linux package manager works like this with /myapps analogous to what /usr is i.e a default convention as to where files should be kept . Compilation is not mandatory unless you want to optimize like the gentoo installation . In other words I think what most package manager do is :
1) Requirements check
2) Copy/Paste of pre-compiled stuff to a standard location like /usr/lib /usr/bin
3) Do a menu update
Some preconditions in the first machine :
Install everything within this directory and not outside of it . It is run as a normal user and no sudo .
In Windows I think this is going to be challenging because of registry etc which I am not sure like normal file system concept . But in *nix should this work as simple as that ?