pdf-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [pdf-devel] [flyspray] Deprecate nocheck in favour of CVS check


From: Pablo Vasquez
Subject: Re: [pdf-devel] [flyspray] Deprecate nocheck in favour of CVS check
Date: Thu, 6 Aug 2009 08:09:32 -0300

Do you think it's OK for me to take this task?
I have already got it compile, and made some tests run.

On Thu, Aug 6, 2009 at 6:59 AM, GNU PDF Library<address@hidden> wrote:
> THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
>
> A new Flyspray task has been opened.  Details are below.
> User who did this - Jose E. Marchesi (jemarch)
> Attached to Project - GNU PDF Library
> Summary - Deprecate nocheck in favour of CVS check
> Task Type - Sporadic Task
> Category - Build System
> Status - NEXT
> Assigned To - Operating System - All
> Severity - Medium
> Priority - Normal
> Reported Version - START
> Due in Version - BASE-LAYER-0
> Due Date - Undecided
> Details - Currently we are using a simple 'check' replacement named
> 'nocheck' to run the unit tests in mingw32 with wine.
>
> nocheck does not provide support for fixtures nor other advanced
> capabilities of 'check'.  Fortunately, it seems that the CVS version of
> 'check' (available on http://check.sf.net) is supporting mingw32 in no-fork
> mode.
>
> The steps of this task are:
>
> 1. Try the CVS version of check and determine if it is able to run our unit
> tests in mingw32 using wine.
> 2. Communicate the results of the investigation to pdf-devel@
>
> At that point we will decide what to do with nocheck: to keep it in the
> sources tree for future uses, or to completely remove it.
>
>
>
> More information can be found at the following URL:
> http://gnupdf.org/flyspray/index.php?do=details&task_id=108
>
> You are receiving this message because you have requested it from the
> Flyspray bugtracking system.  If you did not expect this message or don't
> want to receive mails in future, you can change your notification settings
> at the URL shown above.
>
>
>




reply via email to

[Prev in Thread] Current Thread [Next in Thread]