Hi,
Sorry if this question has already been covered, I couldn't find anything about it when searchin this forum.
I'm trying to script a "smart" network deployment so we can get various vray versions running, ie: stable, test and nightly builds. Using a quiet command line install seem appropriated but I'm still facing two difficulties :
system : OSX SL
app : maya 2012 / vray 2.x
- locally modified / installed files :
Some files are directly copied / modified in maya : shared libraries (libvray.dylib etc.) and common mel scripts … is there a reliable way to "programmatically" identify these files ? I would like to be able to relocate things since we build DYLD_LIBRARY_PATH and MAYA_XXX_PATH based on custom environment variables.
- uninstallation
When installing a new version, the vray installer will try to uninstall the "old one", it is really annoying since I don't want to break previous deployments. What is the process used to detect this ? Is there a way to avoid the uninstall step, or just cheat to "hide" things so the installer won't touch anything ?
Thanks in advance for any advice !
Tonio
Sorry if this question has already been covered, I couldn't find anything about it when searchin this forum.
I'm trying to script a "smart" network deployment so we can get various vray versions running, ie: stable, test and nightly builds. Using a quiet command line install seem appropriated but I'm still facing two difficulties :
system : OSX SL
app : maya 2012 / vray 2.x
- locally modified / installed files :
Some files are directly copied / modified in maya : shared libraries (libvray.dylib etc.) and common mel scripts … is there a reliable way to "programmatically" identify these files ? I would like to be able to relocate things since we build DYLD_LIBRARY_PATH and MAYA_XXX_PATH based on custom environment variables.
- uninstallation
When installing a new version, the vray installer will try to uninstall the "old one", it is really annoying since I don't want to break previous deployments. What is the process used to detect this ? Is there a way to avoid the uninstall step, or just cheat to "hide" things so the installer won't touch anything ?
Thanks in advance for any advice !
Tonio
Comment