I don't think this is significantly different from deploying any other extension although I could be wrong about that. You have to also deploy the gm configuration xml file and the scripts folder as well at least, but if your deploying the profile folder than this should all be included.
On Fri, Mar 19, 2010 at 10:47 AM, johnny <[email protected]> wrote: > I was wondering if there was a way to package greasemonkey for > deployment. I am working on a firefox package with various extensions > for an enterprise deployment, and would like to include greasemonkey > with a few scripts already included. I want the experience to be as > seamless to the user as possible; the user should open firefox and > have no prompts whatsoever but the greasemonkey scripts should be > preinstalled and active on first use. Thanks!! > > -- > You received this message because you are subscribed to the Google Groups > "greasemonkey-users" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/greasemonkey-users?hl=en. > > -- You received this message because you are subscribed to the Google Groups "greasemonkey-users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/greasemonkey-users?hl=en.
