您如何将修复程序放入 Linux 软件包中？
我需要 Python 成像库中的 group4 解码，但为了构建它，我需要将一些更改放入发行版 libtiff-dev 包中。
我以前从未做过这样的事情，我很好奇从哪里开始。我需要对 libtiff 进行的更改是安装 libtiff 后头文件的位置。现在，libtiff 将其头文件放入 /usr/include 中，但它只放入
/usr/include/tiffconf.h
/usr/include/tiff.h
/usr/include/tiffio.h
/usr/include/tiffio.hxx
/usr/include/tiffvers.h
我需要添加的内容：
/usr/include/tif_config.h
/usr/include/tif_dir.h
/usr/include/tiffiop.h
为了实现这一切，我必须使用的 PIL 补丁来自 2006 年，是针对 1.1.6 PIL 库制作的（PIL 现在为 1.1.7），但我很确定如果 PIL 不在发行版中构建，我无法将这些 PIL 补丁放入 pyPI 发行版中。
那么，如何将更改添加到发行版中。我不需要改变 libtiff 中的任何内容，只需改变它的交付方式即可。我需要将这 3 个文件添加到 /usr/include
完成后，我可以将修复程序推送到 PIL 中。
I need group4 decode in the Python Imaging Library, but in order to build it, I need to get some changes put into the distros libtiff-dev packages.
Having never done this kind of thing before, I'm curious about where to start. The changes I need in libtiff are the placement of the header files once libtiff is installed. Right now, libtiff drops its header files into /usr/include, but it only drops in
/usr/include/tiffconf.h
/usr/include/tiff.h
/usr/include/tiffio.h
/usr/include/tiffio.hxx
/usr/include/tiffvers.h
I need to add:
/usr/include/tif_config.h
/usr/include/tif_dir.h
/usr/include/tiffiop.h
The patch in PIL I had to use to get all this going is from 2006 and is made against the 1.1.6 PIL library (PIL is now at 1.1.7), but I'm pretty sure I can't get these patches for PIL into pyPI distribution if it won't build in the distros.
So, how do you get changes into the distros. I don't need to change anything in libtiff, just in the way it gets delivered. I need to get those 3 files added to /usr/include
After that's done, I can push to get the fix into PIL.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
有两种途径可以将修复程序添加到 Linux 发行版中。如果问题是特定于发行版的，那么最好的起点是该发行版的错误跟踪器。您提到丢失文件，这可能是分发问题。 （从您所写的内容中还不清楚为什么这些文件会到处丢失，您确定它们没有被弃用还是其他什么？）
如果它不是特定于发行版的，您仍然可以通过 bug 跟踪器查找分布你可以使用，但你也可以直接去找原作者。作者详细信息通常可以在每个发行版中的某个位置找到。
There are two routes to getting fixes into Linux distributions. If the issue is distribution specific then the best place to start is the bug tracker for that distribution. You mentioned missing files, which is likely to be a distribution issue. (It's not quite clear from what you wrote why those files would be missing everywhere, are you sure they're not deprecated or something?)
If it's not distribution specific you could still go via the bug tracker for the distribution you use, but you could also go directly to the original author. Author details are normally available somewhere within each distribution.