Re: CVS commit: pkgsrc/print/mupdf

[Ryo ONODERA <ryo%tetera.org@localhost>]

Hi,

Greg Troxel <gdt%lexort.com@localhost> writes:

> Ryo ONODERA <ryo%tetera.org@localhost> writes:
>
>> To read some PDF files, I need ICC profile support because
>> without ICC support, the PDF file is difficult to read
>> (very bright green, yellow and cyan are displayed in many places).
>> Ideally graphics/lcms2 should be compatible with print/mupdf.
>> However print/mupdf requires patched version of lcms2
>> and I cannot use graphics/lcms2 as external dependency as is.
>> I may create patched lcms2 package, however its consumer should
>> be print/mupdf only.
>> I would like to avoid such situation.
>
> Not your fault, but that's all crazy.
>
> It would be nice to improve the comment in the Makefile so that the
> longer form of the explanation is readily available, because it really
> is irregular in pkgsrc to use bundled versions.
>
> Ideally there's be a link to an upstream bug report at mupdf, which
> would point to the merge request to lcms2.  If they really intend to use
> a fork, that's more or less an upstream bug, especically if the fork
> doesn't rename.
>
> There is remarkably little easily findable about this but I did find
>
> https://sourceforge.net/p/lcms/mailman/lcms-user/thread/fe77dd64-187f-ad27-5e74-1db97aada80a%40artifex.com/
>
> and thus it really seems like lcms2.art should be a separate package --
> there is basically no hope of resolution.

I have added additional comment to print/mupdf/Makefile.
Anyone can fix/improve the comment.

Thank you.

-- 
Ryo ONODERA // ryo%tetera.org@localhost
PGP fingerprint = 82A2 DC91 76E0 A10A 8ABB  FD1B F404 27FA C7D1 15F3