Re: Bug#287839: ITP: mxml -- small XML parsing library
On Friday 31 December 2021 08:38 am, Eduardo Marcel Macan wrote: I call dibs on his time machine ;-) Daniel -- /--- Daniel Burrows [EMAIL PROTECTED] --\ | Microsoft, n: | | A company that makes pretty good mice. | \- A duck! -- http://www.python.org / pgphFDVekdxD3.pgp Description: PGP signature
Re: Bug#287839: ITP: mxml -- small XML parsing library
hoi :) On Mon, Jan 03, 2005 at 09:13:54AM -0200, Eduardo Marcel Macan wrote: 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. so when you only want zyn to work perhaps it's better to modify it to use libxml2 (you already described that the library APIs is very similar) than to introduce a new library which is only used by one package. -- Martin Waitz signature.asc Description: Digital signature
Re: Bug#287839: ITP: mxml -- small XML parsing library
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 [EMAIL PROTECTED] writes: Scripsit Roger Leigh [EMAIL PROTECTED] Marcelo E. Magallon [EMAIL PROTECTED] 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/Linuxhttp://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-
Re: Bug#287839: ITP: mxml -- small XML parsing library
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Eduardo Marcel Macan [EMAIL PROTECTED] writes: Sorry, I quoted the upstream description, I have a preliminary package ready and it will be uploaded as soon as I make it clean. If you would like someone to check it, I would be happy to review it. 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...) If upstream do not version it, it may cause future problems if you do Debian-specific soname versioning (consider what happens if upstream enable versioning in 6 months). If you require shared libraries, I'm sure Mike Sweet would consider adding support (have you asked?). Otherwise, perhaps static only would be safest for now. 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. It looks quite cool. 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 :) I would certainly be interested. I may even be able to get libgimpprint using it (instead of the customised form we have embedded currently). I also have uses for it in other projects, where libxml2 is not suitable. Regards, Roger - -- Roger Leigh Printing on GNU/Linux? http://gimp-print.sourceforge.net/ Debian GNU/Linuxhttp://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/ iD8DBQFB2XCjVcFcaSW/uEgRAt5gAKDfl/4eqq7UZtHusSU1XnCBHzquTwCgoR/j /G1/zzwxq1PfIfOqw+5zA2Y= =cOMo -END PGP SIGNATURE-
Re: Bug#287839: ITP: mxml -- small XML parsing library
Hello, On Thu, Dec 30, 2004 at 10:58:08PM +, Roger Leigh wrote: Marcelo E. Magallon [EMAIL PROTECTED] writes: On Fri, Dec 31, 2021 at 10:38:46AM -0300, Eduardo Marcel Macan wrote: Mini-XML is a small XML parsing library that you can use to read XML and XML-like data files in your application without requiring large non-standard libraries. Mini-XML only requires an ANSI C compatible compiler (GCC works, as do most vendors' ANSI C compilers) and a make program. You mean unlike libxml2? Package: libxml2 Depends: libc6 (= 2.3.2.ds1-4), zlib1g (= 1:1.2.1) I wonder at which other library is upstream taking shots... not Xerces and not libxmlparse. You might want to include relevant information, like (lack of) validation, external loading, UTF-8, namespaces and the like. mxml is intended to be minimal, as a counter to libxml2 bloat (and it *is* a bloated monster). If you are looking for a tiny tool to handle xml within C programs I suggest that you take a look at flexml. It is based on flex. Unfortunately it works with the old-flex. I had not the time to help patching it so that is works with flex. I am sure that the upstream author will accept to recieve patches. Cheers, -- Pierre Machard [EMAIL PROTECTED] http://debian.org GPG: 1024D/23706F87 : B906 A53F 84E0 49B6 6CF7 82C2 B3A0 2D66 2370 6F87 signature.asc Description: Digital signature
