The only think that worries me about this approach it that it leads
to large number of different environments we would need to test.
Windows ran into a similar problem with DLL dependencies that
increased the chance of random failures.
On Oct 11, 2007, at 10:35 AM, Heikki Toivonen wrote:
While Andi was putting together a Leopard branch of Chandler, he found
out that Leopard ships with a lot of stuff that Chandler can use,
so we
don't need to build and ship that for Leopard.
I just got a follow-up idea to that.
What if we made a combined network installer and Chandler launcher for
Leopard? Basically it would check if all packages it needs are
installed
and if so, launch Chandler. Otherwise run easy_install on the missing
stuff and launch Chandler after that. So something like this in code
(should put in UI for install parts of course but you get the idea):
Chandler.py
...
try:
import M2Crypto
except ImportError:
os.system("easy_install M2Crypto")
...
realMain()
--
Heikki Toivonen
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev
