Re: Bug#287839: ITP: mxml -- small XML parsing library

[Eduardo Marcel Macan <macan@debian.org>]

Sorry, I quoted the upstream description, I have a preliminary package 
ready and it will be
uploaded as soon as I make it clean. The upstream author provides only a 
static version of
the library, so I'm having to check lots of things I never had to deal 
with in order to do it
right (It seems I'll have to take care of sonames and the like myself 
and that's something
I'd prefer to avoid, but anyway...) I know the basics of XML and don't 
really have
any experience using XML libraries myself,  I'm packaging it  because 
zynaddsubfx
uses it to implement an "xml-like" instrument definition, and zyn is one 
of my main
interests.

I think that I'd be a better "comaintainer" of this package than the 
only one
responsible. The ITP seems to have attracted attention, I won't mind if 
someone
offers his help to maintain, or even adopt it. Really :)

Up to now, thank you guys for the comments on the description I attached 
to the
ITP,  they'll be incorporated into my package description.

Roger Leigh wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Henning Makholm <henning@makholm.net> writes:
>
>  
>
> > Scripsit Roger Leigh <rleigh@whinlatter.ukfsn.org>
> >    
> >
> > > "Marcelo E. Magallon" <mmagallo@debian.org> writes:
> > >      
> > >
> > > > After reading your post I wonder if "without requiring large
> > > > non-standard libraries" actually was meant to be read as "without
> > > > requiring libxml2" (i.e. the "large non-standard library" meant here is
> > > > libxml2).
> > > >        
> > > Yes, you would be correct.  It was explicitly intended as a drop-in
> > > replacement.  All it required was a few regexes to change the prefix
> > > on the function and datatype names.
> > >      
> > If the rationale for the package is to avoid having libxml2 on the
> > system, and it is a a partial drop-in replacement, wouldn't it make
> > sense to let the package
> >
> >  1. provide libxml.so.2 with the *same* function names as the real thing
> >
> >  2. conflict with libxml2
> >
> >  3. contain a shlibdeps file that make client packages depend on
> >     libmxml2 | libxml2
> >
> > (Predicted response: Of course not. That would lead to madness).
> >    
>
> :-)
>
> Any program that used the full features of libxml2 would break.  They
> are not so similar as to be binary-compatible; they just have a
> similar API for the libxml2 "tree" interface.
>
>
> - -- 
> Roger Leigh
>                Printing on GNU/Linux?  http://gimp-print.sourceforge.net/
>                Debian GNU/Linux        http://www.debian.org/
>                GPG Public Key: 0x25BFB848.  Please sign and encrypt your mail.
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.5 (GNU/Linux)
> Comment: Processed by Mailcrypt 3.5.8 <http://mailcrypt.sourceforge.net/>
>
> iD8DBQFB1c56VcFcaSW/uEgRAssgAKDBRVb7zkhIbINxwcYxOx+GzaOL/QCg48We
> lkhJGZkSj6D2b4D1ntF3ecE=
> =P/qA
> -----END PGP SIGNATURE-----
>
>
>