As long as you have a solution grouping all those features, SharePoint Installer will deploy them to you in the next-next-finish way, and depending on the scope of the features they need to be activated thru the Manage Features web interface inside the Site Collection / Web.
A:
F.Aquino
2010-02-02 12:22:44
How can i group all the dependencies of the sharepoint site and developed a wsp file contains the complete package of the site (ready to deploy)?
Ramiz Uddin
2010-02-02 12:34:23
Short Answer is WSPBuilder (http://www.codeplex.com/wspbuilder) if you have Visual Studio it will be much easier ( http://www.sharepointbriefing.com/features/article.php/3849011/Developing-SharePoint-Solutions-in-Visual-Studio-Using-WSPBuilder.htm and http://www.zimmergren.net/archive/2009/04/08/wspbuilder-walkthrough-of-the-visual-studio-add-in.aspx ), if you dont here's the command line: http://sharepointcoding.wordpress.com/2009/02/02/wspbuilder-correct-syntax/
F.Aquino
2010-02-02 13:01:53
A:
There is no silver bullet to this. If you migrate from server A to B you'll have to do an inventory on what is installed on server A and provision that on server B. You can look at what Solutions are installed on Central Administration, what webparts are available in the site, what software is installed on the server, etc.
This error regarding WebTemplate #75805 is caused by your target server not having a custom template. Most likely your target server is missing the fantastic 40 or so, download here. There is no way to be sure since anyone can use those numbers but it seems to be the "JRIM JobRequisition" template.
ArjanP
2010-02-02 23:46:21