有关创建安装程序的文献
有没有关于安装程序系统创建的好的文献（或其他信息来源）？我们已经选择了 5 种不同的产品（例如 IzPack、InstallBuilder，...），我们想要使用这些产品进行原型设计，目前正在寻找有关最佳实践以及如何解决此类问题的更多信息。 已经感谢您的回答。
is there any good literature (or other sources of information) covering the creation of installer systems? We already selected 5 different products (e.g. IzPack, InstallBuilder, ...) we want to prototype with and are currently looking for some more information regarding best practices and how to tackle a thing like that.
Thanks already for the answers.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
许多安装程序系统尝试抽象各种目标操作系统（Windows 7、Vista、Linux、Mac OS X、Windows XP 等）之间的差异，以便您可以专注于简单地打包您的产品。有时安装人员做得很好，有时却惨败。尝试找出安装程序抽象不完整的地方，并使用特定操作系统打包指南创建特定于目标的代码。
例如，您的安装程序可能需要使用除用于运行安装程序的用户之外的用户的帐户凭据来运行脚本。安装程序框架可能无法在所有操作系统上很好地支持这一点。
还要认识到，一些用户/客户更喜欢纯粹的本机安装对象（RPM、DEB、MSI 等），这些对象可以与他们自己的部署和/或自动化工具集成。
Many of the installer systems try to abstract the differences among various target operating systems (Windows 7, Vista, Linux, Mac OS X, Windows XP, etc.) so that you can concentrate on simply packaging your product. Sometimes the installers do this well, other times they fail miserably. Try to find out where the installers abstractions are incomplete and create target-specific code using specific operating system packaging guides.
For example, your installer may need to run a script using the account credentials of a user other than the one being used to run the installer. This might not be well supported on all operating systems by the installer framework.
Also recognize that some users/customers would prefer purely native installation objects (RPM, DEB, MSI, etc.) which can be integrated with their own deployment and/or automation tools.