[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: NSXML* classes changed to use libxml2 directly... Should we merge th
From: |
Gregory Casamento |
Subject: |
Re: NSXML* classes changed to use libxml2 directly... Should we merge this into the trunk? |
Date: |
Tue, 24 Jan 2012 07:04:24 -0500 |
Riccardo,
Well, without libxml2 none of the NSXML* classes or GSXML classes will
work. I believe that nib reading will also cease to function, we
won't be able to read XML based plists either. I believe it already
is a hard dependency at this point. I'll need to check by removing
it from my system when I have the chance to do that.
In any case, I see no problem with it being a hard dependency or with
putting it in prior to FOSDEM given that the existing classes have
never worked.
GC
On Tue, Jan 24, 2012 at 3:07 AM, Riccardo Mottola
<address@hidden> wrote:
> Hi,
>
> On 01/23/2012 06:17 PM, Gregory Casamento wrote:
>>
>> For this reason it was decided to change the implementation to use
>> libxml2. Currently the branch I created to develop these changes
>> (nsxml_libxml2_changes) is much more mature and functional than the
>> code that is currently on the trunk.
>>
>> I am soliciting the opinion of the group regarding adding this code
>> into the trunk once it is ready so that people don't look at the
>> already obsolete code on the trunk and begin making changes that are
>> not relavant to the current direction it is going.
>>
>> Please let me know what all of you think.
>
> I think it is a fine idea to have a more complete implementation.
>
> I think it is good to do that after the base release of the code freeze
> (after FOSDEM esentially).
>
> My other thought is that libxml2 should not become a hard dependency, so
> everything should compile, of course without having the more complete XML
> functionality. That's useful for a lean base and requires perhaps some make
> tricks, configure already detects libxml2.
>
> Riccardo
>
>
> _______________________________________________
> Gnustep-dev mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/gnustep-dev
--
Gregory Casamento
Open Logic Corporation, Principal Consultant
yahoo/skype: greg_casamento, aol: gjcasa
(240)274-9630 (Cell)
http://www.gnustep.org
http://heronsperch.blogspot.com
- NSXML* classes changed to use libxml2 directly... Should we merge this into the trunk?, Gregory Casamento, 2012/01/23
- Re: NSXML* classes changed to use libxml2 directly... Should we merge this into the trunk?, Ivan Vučica, 2012/01/23
- Re: NSXML* classes changed to use libxml2 directly... Should we merge this into the trunk?, Riccardo Mottola, 2012/01/24
- Re: NSXML* classes changed to use libxml2 directly... Should we merge this into the trunk?,
Gregory Casamento <=
- Re: NSXML* classes changed to use libxml2 directly... Should we merge this into the trunk?, Richard Frith-Macdonald, 2012/01/24
- Re: NSXML* classes changed to use libxml2 directly... Should we merge this into the trunk?, Riccardo Mottola, 2012/01/25
- Re: NSXML* classes changed to use libxml2 directly... Should we merge this into the trunk?, Gregory Casamento, 2012/01/25
- Re: NSXML* classes changed to use libxml2 directly... Should we merge this into the trunk?, Fred Kiefer, 2012/01/25
- Re: NSXML* classes changed to use libxml2 directly... Should we merge this into the trunk?, Riccardo Mottola, 2012/01/25
- Re: NSXML* classes changed to use libxml2 directly... Should we merge this into the trunk?, Ivan Vučica, 2012/01/25
- Re: NSXML* classes changed to use libxml2 directly... Should we merge this into the trunk?, Riccardo Mottola, 2012/01/25
- Re: NSXML* classes changed to use libxml2 directly... Should we merge this into the trunk?, Ivan Vučica, 2012/01/25
- Re: NSXML* classes changed to use libxml2 directly... Should we merge this into the trunk?, Riccardo Mottola, 2012/01/25
- Re: NSXML* classes changed to use libxml2 directly... Should we merge this into the trunk?, Gregory Casamento, 2012/01/25