gnustep-dev
[Top][All Lists]
Advanced

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

Re: [Debian GNUstep maintainers] request for help: oolite


From: Ivan Vučica
Subject: Re: [Debian GNUstep maintainers] request for help: oolite
Date: Sat, 6 Aug 2016 18:54:07 +0100

Yes, I think that's what was stated in the sentence "a patch for 1.24.9 in Debian to add/use exitLock might be an option" means 0:-)

On Fri, Aug 5, 2016 at 4:22 PM, Eric Heintzmann <address@hidden> wrote:
Hi,


Le 01/08/2016 à 13:51, Richard Frith-Macdonald a écrit :
>> On 1 Aug 2016, at 12:38, Ivan Vučica <address@hidden> wrote:
>>
>> This was my guess too, but it seemed like the use of exitLock is quite limited. I was not aware it was a recent change :-)
>>
>> Aside from someone trying to ask Oolite to fix their init, should we also cut a release of base then?
>
> I don't think base is anywhere near ready for the 1.25.0 release yet (but it's far too much changed and binary incompatible  for another 1.24.?).
>
> I would imagine a 1 line fix to explicitly initialise (for instance) NSDate might solve things in Oolite.
>
> Alternatively, a patch for 1.24.9 in Debian to add/use exitLock might be an option.
Now gnustep-make is uploaded, I'm going to prepare an upload this
week-end to close the RC bug in gnustep-base package( by disabling
concurrent.m test).
Do you think that add/use exitLock is preferable ?

Eric


reply via email to

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