On Mon, 2 Aug 2010 22:34:20 +0200
Jeffrey Ratcliffe <[email protected]> wrote:

> On 2 August 2010 21:48, Neil Williams <[email protected]> wrote:
> > It is possible (even likely) that libforks-perl will have to be removed from
> > testing but it would appear that gscan2pdf could revert to the internal perl
> > threading support (as in previous releases) as part of the fix for the RC 
> > bug
> > against gscan2pdf (#589796).
 
> gscan2pdf has never used Perl's threading module, as libsane-perl,
> which is what is handled in the thread, is not thread-safe.

Then maybe gscan2pdf should not try to use threads at all. If you know
that a dependency is not threadsafe, either do not use threads or find
a different way to implement the functionality of the dependency. e.g.
you might have to write a separate program which entirely wraps the
non-threadsafe functionality and exports data to the threaded front end
as a separate process. Overall, it may be simpler to rewrite gscan2pdf
in a language which has better thread support or not use threads at all.

> > There is a simple patch (prepared by Chris Butler) but there should be some
> > discussion about the options and implications. It seems unlikely that 
> > libforks-
> > perl can be reliably fixed and if converting gscan2pdf to revert to internal
> > perl threading support means that other bugs would appear as regressions, 
> > then
> > maybe gscan2pdf itself would have to be removed alongside libforks-perl.
> 
> This is a huge change, and it would be good to do some extended
> testing before pushing this to unstable. What is the timescale?

Short. If gscan2pdf needs that much work, it will have to be removed
from testing whilst that work goes on, possibly putting the next
gscan2pdf upload into experimental if the changes are that large.

If gscan2pdf cannot make the change, it is likely that gscan2pdf would
also need to be removed.

-- 


Neil Williams
=============
http://www.data-freedom.org/
http://www.nosoftwarepatents.com/
http://www.linux.codehelp.co.uk/

Attachment: pgpj0kaH1Qk3a.pgp
Description: PGP signature

Reply via email to