gnustep-dev
[Top][All Lists]
Advanced

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

Re: GNUstep on OSX


From: Richard Frith-Macdonald
Subject: Re: GNUstep on OSX
Date: Sat, 13 Apr 2013 11:03:07 +0100

On 12 Apr 2013, at 00:14, Ibadinov Marat wrote:

> 
> On Apr 11, 2013, at 1:50 AM, Riccardo Mottola wrote:
> 
>> Hi Ibadinow,
>> 
>> 
>> Ibadinov Marat wrote:
>>> Hello, fellow GNUstepers.
>>> 
>>> For a quite some time i've been maintaining fork of GNUstep primarily
>>> focused on OSX support and reliability.
>>> The first objective is motivated by prevalence of OSX users in
>>> Objective-C user base (the only group people who could help with
>>> GNUstep development).
>>> Second one is simply an obligation to my employer (this forks are used
>>> in production environment right now).
>>> 
>>> I seem to be a little bit tired to be alone on these journey, and am
>>> willing to be a part of a team. So i would like to offer this code
>>> base for you consideration.
>>> Lets try to make you interested, here goes a list of features that i
>>> could remember:
>>> 
>> Seems you maintain a lot of work. My first impulse would be to say:
>> let's check piece after piece: what is good for GNUstep generally? What
>> doesn't clash? and reduce differences piece after piece.
>> Of course, each maintainer should evaluate, so the best thing would be
>> to have patches for only the individual stuff.
> 
> I'm afraid it is not quite possible to do so with ease. All this stuff was 
> developed
> simultaneously, and it will require too much work to separate it.
> But if this is necessary, we'll figure it out somehow.

It would be great to get bugfixes and improvments into trunk ... we do need 
copyright assignment to the FSF, and to do it in managable chunks though.

In particular I'd love a good reliable alternative to FFI, and proper,tested 
SOCKS support.

I've never been really happy with the existing SOCKS code:
I never needed to use it myself and don't know how well it actually works ... 
one of the drawbacks of a project like this is that, if you receive no 
feedback, you never know whether that's because something works flawlessly or 
because nobody has actually tried using it.






reply via email to

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