Hey Graham,
See how it is derived from build classes? I believe that implies that
it is Run() at build time, not post-install. Like Make, MakeInstall,
Copy, etc. They are all done to create a file system to be laid down at
install time.
-Eric
Graham Bloice wrote:
On 23/01/07, Eric Newton <[EMAIL PROTECTED]> wrote:
I do not know of a way to run scripts during the install process as part
of the conary update/recipe. I would _love_ to fix this if you know
how.
I have a compromise for you: I'll modify the zenoss script to do this
in future releases:
http://dev.zenoss.org/trac/ticket/918
A (very) quick scan of the conary docs seems to imply that the package
r.Run() command can run arbitrary shell scripts after installation.
See
http://cvs.rpath.com/conary-docs/public/conary.build.build.Run-class.html
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
