包含 deb 包文件和源代码
我有一个正在为 Ubuntu 创建的应用程序。
我有 Windows 编程背景，习惯于将 WiX 源代码与源代码一起包含在我的源代码管理中。所以它是通过我的来源进行跟踪和更改的。
现在我正在学习deb打包。所有教程都说要下载源代码，然后创建 Debian 文件夹以及用于构建的规则、安装、控制、版权等文件。
没有提及 Debian 文件夹中内容的源代码控制。似乎有很多重要信息，我不想每次需要构建新的 deb 包时都重现。
如果不是这样，我将 debian 文件夹与源代码一起添加到我的源代码管理中。因此，当您下载源代码时，所有打包规则都已准备就绪。
这种方法有什么问题吗？
这样做是否会违反一些包装规则？
为什么 deb 包源文件通常不包含在源代码中？
I have an application which I am creating for Ubuntu.
I come from a windows programming background and I am used to including the WiX source in my source control along side my source code. So it is tracked and changed with my source.
Now I am learning about deb packaging. All the tutorials say to download the source and then create the Debian folder and the rules, install, control, copyright etc files for doing the build.
There is no mention of source control for the stuff in the Debian folder. There seems like quite a lot of important information I would rather not reproduce everytime I need to build a new deb package.
If instead of this I add the debian folder to my source control along side my source. So when you download the source all the packaging rules are there ready do go.
Are there any problems with this approach?
Will I be breaking some packing rules by doing this?
Why are deb package source files not usually included in the source code?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
这实际上是受到鼓励的，甚至有直接从 SVN 和 Git。它们还提供标准化布局和其他功能，如果您希望您的软件包包含在 Debian 中，这些功能非常有用。
This is actually encouraged and there are even tools for automatically building packages directly from SVN and Git. They also provide standardized layout and other functionality that is useful if you want your package including in Debian.
这应该可以正常工作，并且许多软件包的源代码管理中都有一个 debian 文件夹。
That should work fine, and many software packages have a debian folder in their source control.