[vtk-developers] vtkfreetype update

[David Cole]

Thanks for the input...... I tend to agree, but "security fixes" should be
incorporated when they don't break anything.

Since this one "breaks" stuff and I'm not clear either on whether there
really is a security issue with what VTK uses/exposes of the freetype
implementation, then .... better to leave well enough alone unless somebody
has a demonstrable problem.

Sean, let's resolve this bug as "won't fix" for now. If somebody disagrees,
or has better evidence that VTK needs the security fixes, then we can
re-open it at that time.


Thanks,
David Cole



On Fri, Jul 18, 2008 at 2:21 PM, Sebastien BARRE <
sebastien.barre at kitware.com> wrote:

>  At 7/18/2008 01:43 PM, David Cole wrote:
>
> Sean McBride has been investigating upgrading vtk's freetype to 2.3.6 to
> include some security fixes in the freetype code.
>
> It's listed as this bug in the VTK bug tracker:
>  http://public.kitware.com/Bug/view.php?id=7199
>
> Is there somebody on this list who is a "VTK / text rendering / embedded
> fonts" expert that could have a quick discussion with one of the freetype
> devs about why some of the text rendering is different (and maybe "worse")
> than before upgrading to 2.3.6...? If so, reply to me and I'll connect you
> guys.
>
> Sean is holding off committing this bug fix to CVS HEAD until we make sure
> it's what we want to do.
>
> Does anybody have a strong opinion either way -- what's more important:
>
>   (1) getting the security fixes into VTK?
>       or
>   (2) maintaining pixel-perfect-fidelity of rendered text?
>
>
> If it ain't broke, dont' fix it. Each time we update it, we risk of losing
> any specific patch that was made for VTK (hopefully not that many lately,
> usually only fixes to the freetype build process).
>
> The bug entry is not clear about what the problem is with respect to VTK.
> My gut feeling is that libs in Utilities/ should only be updated when a
> major feature is needed, or a really big bug.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/vtk-developers/attachments/20080718/84254a33/attachment.html>