去年，2009 年 GSoC，我参加了一个名为 Winlibre 的组织。基本想法是拥有一个类似于 Aptitude（或 Apt-get）的项目和一个类似于 Synaptic 的 GUI，但适用于 Windows，并且（最初）只保留开源软件。这个项目还不错，我们完成了我们认为是一个很好的起点，但不幸的是，由于开发人员的职业不同，该项目自从 GSoC 完成以来几乎一直处于闲置状态。现在，我有一些精力、时间和兴趣来尝试继续这种发展。该项目分为 3 个部分：存储库服务器（我参与其中，用于存储和提供包和文件）、开发人员的包创建器以及主应用程序，即 apt-get 及其 GUI。
我一直在思考这个项目，我想到的第一个问题是……这个项目实际上对开发人员和 Windows 用户有用吗？请记住，这个想法是解决依赖关系问题，并“干净地”安装软件包。我不是 Windows 开发人员，只是一个临时用户，所以我对于如何处理事情确实没有太多经验，但据我所知，所有安装程序都会处理这些依赖项。 Windows 开发人员愿意从安装程序切换到处理开源软件安装的软件包方式吗？或者为已经存在的安装程序创建包就可以了？
包的概念与 .deb 或 .rpm 文件基本相同。
我还有一些其他问题，但基本上我想确保它在某种程度上对用户和 Windows 开发人员有用，以及开发人员是否会发现这个项目有趣。如果您有任何问题、反馈、建议或批评，请随时发布。
谢谢！！
Last year, in 2009 GSoC, I participated with an organization called Winlibre. The basic idea is having a project similar to Aptitude (or Apt-get) and a GUI like Synaptic but for Windows and just to hold (initially), only open source software. The project was just ok, we finished what we considered was a good starting point but unfortunately, due to different occupations of the developers, the project has been idle almost since GSoC finished. Now, I have some energy, time and interest to try to continue this development. The project was divided in 3 parts: A repository server (which i worked on, and which was going to store and serve packages and files), a package creator for developers, and the main app, which is apt-get and its GUI.
I have been thinking about the project, and the first question that came to my mind is.. actually is this project useful for developers and Windows users? Keep in mind that the idea is to solve dependencies problems, and install packages "cleanly". I'm not a Windows developer and just a casual user, so i really don't have a lot of experience on how things are handled there, but as far as I have seen, all installers handle those dependencies. Will windows developers be willing to switch from installers to a packages way of handling installations of Open source Software? Or it's just ok to create packages for already existing installers?
The packages concept is basically the same as .deb or .rpm files.
I still have some other questions, but basically i would like to make sure that it's useful in someway to users and Windows developers, and if developers would find this project interesting. If you have any questions, feedback, suggestions or criticisms, please don't hesitate posting them.
Thanks!!
发布评论
评论（4）
请务必研究以前在这方面的努力。谷歌发现了一些类似/相关的努力。
http://en.wikipedia.org/wiki/Package_management_system#Microsoft_Windows
http://windows-get.sourceforge.net
http://pina.plasmite.com
IIRC 在某个时候有一个针对 Windows 的 rpm
另外我认为最近新闻中出现了一些人（曾经在 MS 工作）这基本上是在启动一个非常相似的项目。我现在找不到这个的链接。
但无论如何，是的，如果有这样一个标准工具和存储库，那就太棒了。
be sure to research previous efforts on this. Google turns up several similar/relevant efforts.
http://en.wikipedia.org/wiki/Package_management_system#Microsoft_Windows
http://windows-get.sourceforge.net
http://pina.plasmite.com
IIRC there was an rpm for windows at some point
Also I think there was some guy (who used to work at MS) in the news recently that basically is starting up a very similar project. I can't find a link to this now.
But anyway, yeah, it would be awesome if there was such a standard tool and repository.
我只能代表自己说话，但显然我绝对可以使用这样的工具，因为我通过谷歌搜索找到了你的帖子！ ;)
我对该工具的两个用例如下：
1. 我通常会尽可能避免重新安装系统（事实上，我这样做只是为了每隔几年切换到合理的（不是每一个）新版本的 Windows 或设置新计算机）。但我仍然希望我的软件是最新的。我既不想访问所有网页并手动检查新版本的 Doxygen、Graphviz 和最新版本的 MikTeX 是否存在兼容性问题，也不想导航到下载页面并自行运行设置。我只想安排一个（！）工具，它检查是否有新的更新，并更新那些不与任何其他应用程序版本冲突的应用程序。
我对 .deb 或 .rpm 的体系结构了解不够，但恕我直言，最合理的方法是维护一个仅包含名称、版本、依赖项和不同版本下载位置的数据库。我的意思是，大多数可用于 Windows 的工具无论如何都提供 .msi 包，（我猜）是应用程序本身和一些自定义安装属性（真的不确定如何处理脚本，但我知道在 Visual Studio 中创建 MSI创建自定义安装步骤的能力非常有限，我只能想象这是由于 MSI 协议的限制）。
我想 Windows 用户必须使用 GUI ;) 但我个人更喜欢使用控制台处理设置的附加功能。
嗯，我喜欢这个想法，并且很想在未来听到这个（或这样的）工具的消息。
干杯
I can only speak for myself, but obviously I could definitely make use of such a tool as I found your post through googling! ;)
My two use cases for this tool would the following ones:
1. I generally avoid to re-install my system as long as possible (in fact I manage to do so only for switching to a reasonable (not each an every) new version of Windows every few years or to setup new computers). But still I'd like my software to be up-to-date. Neither do I want to have to go to all the web pages and check manually if there are compatibility issues with the new version of Doxygen, Graphviz and the latest version of MikTeX for example, nor do I want to have to navigate to the download pages and run the setups all by myself. I just want to schedule ONE SINGLE (!) tool, which checks whether there are new updates or not and updates those applications which are not in conflict with any other application version.
I don't know enough about the architecture of .deb or .rpm but IMHO the most reasonable would be to maintain a DB with only the names, versions, dependencies and the location of the different versions' download locations. I mean, most of the tools available for Windows provide .msi packages anyways, which (I guess) is the application itself and some custom installation properties (really not sure how scripting is handled, but I know that creating a MSI in Visual Studio has very limited abilities to create custom installation steps and I can only imagine this is due to limitations of MSI protocol).
I guess a GUI will be mandatory for Windows users ;) but I personally would prefer the additional ability to handle the setups with the console.
Well, I like the idea and would love to hear from that (or such a) tool in the future.
Cheers
查看 NSIS。它是一个开源 MSI 创建者。您也许可以将其用作包创建软件的一部分。
http://nsis.sourceforge.net/Main_Page
Check out NSIS. It's an open source MSI creator. You might be able to use it as part of your package creation software.
http://nsis.sourceforge.net/Main_Page
对于 ALT-.Net 工具/lib 堆栈，在这个方向上有一些提供：Horn Get
然而，现实世界项目中的可用性一直是 这个问题的主题。
For the ALT-.Net tool/lib stack there have been some affords in this direction: Horn Get
However, the usability in a real world project has been subject in this SO question.