On 21 October 2010 08:15, Jimmy O'Regan <[email protected]> wrote: > That doesn't sound right. I'll check into it at the mentor summit.
>From [1] (or the libpkg-guide package on a Debian-based distro): There are packages like libc6, which contain multiple shared libraries in one package. This is not encouraged. [2] It becomes more complex and more difficult to handle complex upgrade patterns. Regards Jeff [1] http://www.netfort.gr.jp/~dancer/column/libpkg-guide/libpkg-guide.html#naminglibpkg [2] This is the case unless it is confident that shared libraries will not change interfaces independently, or compatibility issues are carefully handled. In general, when shared libraries are split, there is no reason upstream will keep changes to interfaces synchronised. -- You received this message because you are subscribed to the Google Groups "tesseract-ocr" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/tesseract-ocr?hl=en.
