From cameracafffe at live.it  Thu Jan  8 18:12:39 2009
From: cameracafffe at live.it (andrea bianchi)
Date: Thu, 8 Jan 2009 18:12:39 +0100
Subject: [Expat-discuss] (no subject)
Message-ID: <COL114-W31B0D750483D2F1F0462E8C7DC0@phx.gbl>


Hi, I'm a developer and I'm interesting to your XML 
parser. 
 
I've a question: is there a routine that take a 
text input in a void* - char* buffer and give an other text in another void* - 
char* buffer? Idon't know if you understand my question... sorry for my bad 
english, I'm Italian :)
 
Thanks a lot
_________________________________________________________________
Quali sono le pi? cliccate della settimana?
http://livesearch.it.msn.com/

From dbn.lists at gmail.com  Fri Jan 16 20:53:55 2009
From: dbn.lists at gmail.com (Dan Nicholson)
Date: Fri, 16 Jan 2009 11:53:55 -0800
Subject: [Expat-discuss] Time for a new release?
Message-ID: <91705d080901161153p3380307ax16ea7b94dc0deecc@mail.gmail.com>

Hi,

There only been a couple of bugfixes since the 2.0.1 release, but
maybe it's time to get them out to everyone. Plus, I'd like to see the
expat pkg-config file get into a tarball. What do you think?

--
Dan

From marco.maggi-ipsu at poste.it  Sat Jan 17 08:24:49 2009
From: marco.maggi-ipsu at poste.it (Marco Maggi)
Date: Sat, 17 Jan 2009 08:24:49 +0100
Subject: [Expat-discuss] Time for a new release?
Message-ID: <KDLTXE$FBFD24931455F5092A24A289113D5FC5@poste.it>

"Dan Nicholson" wrote:
> There only been a couple of bugfixes since
> the 2.0.1 release, but maybe it's time to
> get them out to everyone.

I step in this thread as a new user.

In the process of testing the foreign
functions interface callback features
of a set of Scheme language implementations,
I have started a binding to Expat.

The first thing I noticed is that the
documentation is in bad shape.  This is
a real problem for me, so I started by
reformatting it to Texinfo[1].

It would really help me to have this doc
included in the official Expat distribution,
and to have it reviewed by some of the
maintainers.

There are things that need to be improved,
for example the "api handlers" node needs
to be split into subsections.

There is a number of stylistic fixes and
clarifications I would like to ask to you,
but I have no time right now.

So for the time being can you gather the
file and include it?

[1] http://github.com/marcomaggi/nausicaa/blob/b9ab28bd294a48a62f344cc793350727700a6ea8/expat/doc/expat.texi
-- 
Marco Maggi



From fdrake at acm.org  Sat Jan 17 19:52:34 2009
From: fdrake at acm.org (Fred Drake)
Date: Sat, 17 Jan 2009 13:52:34 -0500
Subject: [Expat-discuss] Time for a new release?
In-Reply-To: <KDLTXE$FBFD24931455F5092A24A289113D5FC5@poste.it>
References: <KDLTXE$FBFD24931455F5092A24A289113D5FC5@poste.it>
Message-ID: <0DFACA6E-5420-4087-9046-C49CF756818D@acm.org>

On Jan 17, 2009, at 2:24 AM, Marco Maggi wrote:
> In the process of testing the foreign
> functions interface callback features
> of a set of Scheme language implementations,
> I have started a binding to Expat.

Wonderful!  What Scheme implementations are you supporting?

> The first thing I noticed is that the
> documentation is in bad shape.  This is
> a real problem for me, so I started by
> reformatting it to Texinfo[1].

Why Texinfo?  I'm a little surprised that's used any more.

There are two separate concerns here:

1. Format (HTML v. Texinfo v. anything else).

2. Content.

I'd rather separate those concerns; whatever content changes should be  
made to the current format, and a format conversion should be  
considered on it's own merits.

I'm not opposed to changing the documentation format, but I am opposed  
to changing it without planning.  I think it's also important that  
there be only one format.


   -Fred

-- 
Fred Drake   <fdrake at acm.org>


From karl at waclawek.net  Sat Jan 17 20:07:51 2009
From: karl at waclawek.net (Karl Waclawek)
Date: Sat, 17 Jan 2009 14:07:51 -0500
Subject: [Expat-discuss] Time for a new release?
In-Reply-To: <91705d080901161153p3380307ax16ea7b94dc0deecc@mail.gmail.com>
References: <91705d080901161153p3380307ax16ea7b94dc0deecc@mail.gmail.com>
Message-ID: <49722C87.6030104@waclawek.net>

Dan Nicholson wrote:
> Hi,
>
> There only been a couple of bugfixes since the 2.0.1 release, but
> maybe it's time to get them out to everyone. Plus, I'd like to see the
> expat pkg-config file get into a tarball. What do you think?
>   

I agree. there should be a new release.

The problem for me is, I am far from being a Unix/Linux build expert, so 
I have no idea how important pkg-config is, and how to evaluate it.
Unfortunately, we don't have anyone active on the Unix/Linux side right 
now. Maybe Fred or Sebastian will pick up the torch.

Karl


From fdrake at acm.org  Sat Jan 17 20:22:39 2009
From: fdrake at acm.org (Fred Drake)
Date: Sat, 17 Jan 2009 14:22:39 -0500
Subject: [Expat-discuss] Time for a new release?
In-Reply-To: <49722C87.6030104@waclawek.net>
References: <91705d080901161153p3380307ax16ea7b94dc0deecc@mail.gmail.com>
	<49722C87.6030104@waclawek.net>
Message-ID: <4E2B83F8-47E4-4ECD-B8B1-CB26BC2E8D5A@acm.org>

On Jan 17, 2009, at 2:07 PM, Karl Waclawek wrote:
> Unfortunately, we don't have anyone active on the Unix/Linux side  
> right now. Maybe Fred or Sebastian will pick up the torch.

I'll try to remember to take a look at the state of things this  
evening; I noticed you've been cleaning house.  :-)


   -Fred

-- 
Fred Drake   <fdrake at acm.org>


From dbn.lists at gmail.com  Sat Jan 17 21:48:38 2009
From: dbn.lists at gmail.com (Dan Nicholson)
Date: Sat, 17 Jan 2009 12:48:38 -0800
Subject: [Expat-discuss] Time for a new release?
In-Reply-To: <49722C87.6030104@waclawek.net>
References: <91705d080901161153p3380307ax16ea7b94dc0deecc@mail.gmail.com>
	<49722C87.6030104@waclawek.net>
Message-ID: <91705d080901171248p702857c0x88bbedf6de501d9@mail.gmail.com>

On Sat, Jan 17, 2009 at 11:07 AM, Karl Waclawek <karl at waclawek.net> wrote:
> Dan Nicholson wrote:
>>
>> Hi,
>>
>> There only been a couple of bugfixes since the 2.0.1 release, but
>> maybe it's time to get them out to everyone. Plus, I'd like to see the
>> expat pkg-config file get into a tarball. What do you think?
>>
>
> I agree. there should be a new release.
>
> The problem for me is, I am far from being a Unix/Linux build expert, so I
> have no idea how important pkg-config is, and how to evaluate it.
> Unfortunately, we don't have anyone active on the Unix/Linux side right now.
> Maybe Fred or Sebastian will pick up the torch.

Well, I wrote the pkg-config patch, and I'm involved in a lot of
different projects helping with packaging. pkg-config is really
helpful for another project that wants to depend on expat. A lot of
Linux distros already ship an expat pkg-config file.

I haven't tried to build expat from CVS in a while, but I don't recall
there being any problems on Linux. I'll make sure that it still works,
though, and send patches for anything wrong I see.

--
Dan

From marco.maggi-ipsu at poste.it  Sat Jan 17 22:57:04 2009
From: marco.maggi-ipsu at poste.it (Marco Maggi)
Date: Sat, 17 Jan 2009 22:57:04 +0100
Subject: [Expat-discuss] Time for a new release?
Message-ID: <KDMYB4$53D072F30B1EB0ECCCA41936DA4606E5@poste.it>

"Fred Drake" wrote:
>> I have started a binding to Expat.
>
>Wonderful!  What Scheme implementations
>are you supporting?

I will tell you whenever I have something
working.

>Why Texinfo?  I'm a little surprised that's
>used any more.

For a number of reasons, most of which are
probably specific to myself.  I have to say
that I am not prepared to "defend" Texinfo,
anyway I will try with the following list
of pros.

Notice that I have pushed a fixed version
of the file[1], which solves problems with
conversion to PDF.

1. I am already sending to you a Texinfo
   version, not LaTeX or Docbook or
   Doxygen or whatever.  :-)

2. We can generate XML source with:

|  $ makeinfo --xml expat.texi

   then... well, we are talking about an XML
   library here...  The DTD is available[2].
   Docbook output is available, too:

|  $ makeinfo --docbook expat.texi

   I cannot speak for the quality of the
   conversion because I never used the XML
   output.  But it is here, so it provides
   an exit strategy from the format.

2. Available human readable output formats
   are: Info, plain text, HTML, DVI, PDF.
   Each of them is generated by issuing a
   single command (no complicated Makefile
   rules are needed, like for LaTeX).

3. Generating output from a Texinfo file
   is fast, even for big documents.

4. A programmer can learn how to edit a
   Texinfo file in a day.  I am available
   to give hints if there is the need.

5. There is a nice Emacs mode to edit Texinfo
   files, which (believe me) allows us to keep
   the documentation in a single file even if
   it becomes huge (I am maintaining a single
   Texinfo file of about 793K).

6. The format is easy, so it is also easy to
   write some Emacs function to automate tasks.
   A lot can be done with simple regular
   expressions.

7. The Info format is readable on a terminal
   and in Emacs, with incremental search and
   autocompletion of node names and index
   entries (available on the terminal, too).

8. There is a huge body of existing documentation
   written in Texinfo (Glibc, GCC, GMP, GSL, MPFR,
   m4, gawk, Emacs, Mailutils), some of the
   documents are very well written.  So it is
   possible to write good documentation in this
   format, and there is interest in keeping the
   format around without ground breaking changes
   in the specification.

I am a terminal die harder, and I am really
satisfied with the Info output.  It is always
my first choice.

According to my taste, the PDF output is good
enough, and the HTML output (although a little
"plain") goes (there is worse stuff around).

Even with an unsophisticated reader like xpdf,
I can browse the PDF output and use the links
from the menu and the index.

The ball is in your court...

[1] http://github.com/marcomaggi/nausicaa/blob/b6e131f5391264fa05bd78d210fcc8f5647b7fac/expat/doc/expat.texi
[2] http://www.gnu.org/software/texinfo/dtd/4.8/texinfo.dtd
-- 
Marco Maggi



From karl at waclawek.net  Sun Jan 18 17:02:12 2009
From: karl at waclawek.net (Karl Waclawek)
Date: Sun, 18 Jan 2009 11:02:12 -0500
Subject: [Expat-discuss] Time for a new release?
In-Reply-To: <91705d080901171248p702857c0x88bbedf6de501d9@mail.gmail.com>
References: <91705d080901161153p3380307ax16ea7b94dc0deecc@mail.gmail.com>	
	<49722C87.6030104@waclawek.net>
	<91705d080901171248p702857c0x88bbedf6de501d9@mail.gmail.com>
Message-ID: <49735284.8080904@waclawek.net>

Dan Nicholson wrote:
> Well, I wrote the pkg-config patch, and I'm involved in a lot of
> different projects helping with packaging. pkg-config is really
> helpful for another project that wants to depend on expat. A lot of
> Linux distros already ship an expat pkg-config file.
>
> I haven't tried to build expat from CVS in a while, but I don't recall
> there being any problems on Linux. I'll make sure that it still works,
> though, and send patches for anything wrong I see.
>
>   

OK, sounds good.

Karl

From dbn.lists at gmail.com  Sun Jan 18 18:45:57 2009
From: dbn.lists at gmail.com (Dan Nicholson)
Date: Sun, 18 Jan 2009 09:45:57 -0800
Subject: [Expat-discuss] Time for a new release?
In-Reply-To: <49735284.8080904@waclawek.net>
References: <91705d080901161153p3380307ax16ea7b94dc0deecc@mail.gmail.com>
	<49722C87.6030104@waclawek.net>
	<91705d080901171248p702857c0x88bbedf6de501d9@mail.gmail.com>
	<49735284.8080904@waclawek.net>
Message-ID: <91705d080901180945h435f9475p60f9d7f6070ca904@mail.gmail.com>

On Sun, Jan 18, 2009 at 8:02 AM, Karl Waclawek <karl at waclawek.net> wrote:
> Dan Nicholson wrote:
>>
>> Well, I wrote the pkg-config patch, and I'm involved in a lot of
>> different projects helping with packaging. pkg-config is really
>> helpful for another project that wants to depend on expat. A lot of
>> Linux distros already ship an expat pkg-config file.
>>
>> I haven't tried to build expat from CVS in a while, but I don't recall
>> there being any problems on Linux. I'll make sure that it still works,
>> though, and send patches for anything wrong I see.
>>
>>
>
> OK, sounds good.

Just tried the build again on Linux x86 and x86_64. Everything seemed
fine. I had a look at fedora and debian's expat packages. Here are
some patches they're applying:

http://cvs.fedora.redhat.com/viewvc/rpms/expat/devel/expat-1.95.8-pedantic.patch?view=markup
http://patch-tracking.debian.net/package/expat/2.0.1-4

I cc'd the package maintainers (at least, who I think they are), to
see if they have any specific input on those patches.

--
Dan

From karl at waclawek.net  Sun Jan 18 21:00:26 2009
From: karl at waclawek.net (Karl Waclawek)
Date: Sun, 18 Jan 2009 15:00:26 -0500
Subject: [Expat-discuss] Time for a new release?
In-Reply-To: <1232302876.5803.32.camel@localhost>
References: <91705d080901161153p3380307ax16ea7b94dc0deecc@mail.gmail.com>	
	<49722C87.6030104@waclawek.net>	
	<91705d080901171248p702857c0x88bbedf6de501d9@mail.gmail.com>	
	<49735284.8080904@waclawek.net>	
	<91705d080901180945h435f9475p60f9d7f6070ca904@mail.gmail.com>
	<1232302876.5803.32.camel@localhost>
Message-ID: <49738A5A.7080704@waclawek.net>

Daniel Leidert wrote:
> Am Sonntag, den 18.01.2009, 09:45 -0800 schrieb Dan Nicholson:
>   
>> Just tried the build again on Linux x86 and x86_64. Everything seemed
>> fine. I had a look at fedora and debian's expat packages. Here are
>> some patches they're applying:
>>
>> http://cvs.fedora.redhat.com/viewvc/rpms/expat/devel/expat-1.95.8-pedantic.patch?view=markup
>> http://patch-tracking.debian.net/package/expat/2.0.1-4
>>
>> I cc'd the package maintainers (at least, who I think they are), to
>> see if they have any specific input on those patches.
>>     
>
> Of course I will do. I first mention the patch, followed by a short
> explanation and the related Debian bug report (the same information can
> also be found in the patch headers).
>
> http://svn.debian.org/wsvn/debian-xml-sgml/packages/expat/trunk/debian/patches/82763_xmlwf_error_out_2.dpatch?op=file&rev=0&sc=0
>
> xmlwf exits with status zero in case of an error. It is common to error
> out with a non-zero exit status. The patch simply makes the application
> exit with status 2 in case of an error.
> http://bugs.debian.org/82763
>
>   

Has this (and other issues) ever been reported to the Expat project on SF?
For instance, from what I can tell, xmlwf returns non-zero for errors in 
quite a few cases (check the usage() calls, or XML_ProcessFile() in 
xmlfile.c.

So I assume, we have a true bug here. This should be posted to 
https://sourceforge.net/tracker2/?atid=110127&group_id=10127

> http://svn.debian.org/wsvn/debian-xml-sgml/packages/expat/trunk/debian/patches/302191_install_expat_config_h.dpatch?op=file&rev=0&sc=0
>
> It seems, some projects (python-4suite) reference the expat_config.h
> header file. The patch simply adds this file to be installed. I'm *not*
> sure, that this patch should be accepted upstream. It might be an error
> to reference expat_config.h in a software source. You should check (I
> can do this too in a few days), why python-4suite references this header
> file. Maybe moving some declarations to the installed header files is
> the solution to go.
> http://bugs.debian.org/302191
>   

expat_config.h is generated for Unix, on Windows it does not exist. It 
should not generally be needed.

> http://svn.debian.org/wsvn/debian-xml-sgml/packages/expat/trunk/debian/patches/342684_libtoolize.dpatch?op=file&rev=0&sc=0
>
> If you use some recent autotools, you can probably safely ignore this
> patch. It simply runs the autotools chain on the source to get a newer
> libtool version to support GNU/kFreeBSD.
> http://bugs.debian.org/342684
> http://bugs.debian.org/439127
>   

Expat always seems to be behind on this area, but I have to leave this 
to our Unix experts.

> http://svn.debian.org/wsvn/debian-xml-sgml/packages/expat/trunk/debian/patches/412786_xmlwf_man_standard_fix.dpatch?op=file&rev=0&sc=0
>
> The SGML file contains a linebreak followed by three dots and and
> parenthesis. The manual page contains the same linebreak. So the next
> line in the manual page starts with the dots. But a leading dot has a
> special meaning. GROFF expects a macro or request name after the dot. So
> it throws a warning and doesn't print these four characters in the
> resulting manual page. The patch simply removes the linebreak as an easy
> solution to the problem.
>
> The second part of the patch removes a wrong statement in the BUGS
> section. There you state, that the XML standard requires the XML
> declaration for well-formedness. But that's not true. The declaration is
> optional, as you can see here:
> http://www.w3.org/TR/2006/REC-xml-20060816/#NT-prolog
> http://bugs.debian.org/412786
>   

Again, it would be nice to have this reported on the bug page. We do not 
normally Google for Expat bugs reported anywhere else.
The SGML has not been updated since 2003. Who is actually using it? 
Anyway, a bug report would be useful, but also a review of the overall 
contents of the SGML file. Maybe we should discard it altogether?

> http://svn.debian.org/wsvn/debian-xml-sgml/packages/expat/trunk/debian/patches/485129_fix_underquotation_in_m4.dpatch?op=file&rev=0&sc=0
>
> In expat.m4 the AM_WITH_EXPAT macro is underquoted. See the paragraph
> starting with "Starting with Automake 1.8, aclocal will warn about all
> underquoted calls to AC_DEFUN [..]":
> http://sources.redhat.com/automake/automake.html#Extending-aclocal
> http://bugs.debian.org/485129
>
> The patch is trivial and safe.
>   

Hope our build experts will do this.

> If you have any further questions or comments about the patches, please
> don't hesitate to contact me.
>
>
> PS: There is still an open bug report, you maybe want to comment/fix:
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=245840
> http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=23;bug=245840
>
> Regards, Daniel
>   

As a general comment, we would like bugs reported to the Expat project, 
as we cannot go around hunting for bug reports elsewhere.
If these bugs have indeed been reported, it would be nice to refer to 
them by the *Expat*  bug tracking number.

Thanks for bringing all of this to our attention.

Karl

From dbn.lists at gmail.com  Sun Jan 18 21:47:23 2009
From: dbn.lists at gmail.com (Dan Nicholson)
Date: Sun, 18 Jan 2009 12:47:23 -0800
Subject: [Expat-discuss] Time for a new release?
In-Reply-To: <49738A5A.7080704@waclawek.net>
References: <91705d080901161153p3380307ax16ea7b94dc0deecc@mail.gmail.com>
	<49722C87.6030104@waclawek.net>
	<91705d080901171248p702857c0x88bbedf6de501d9@mail.gmail.com>
	<49735284.8080904@waclawek.net>
	<91705d080901180945h435f9475p60f9d7f6070ca904@mail.gmail.com>
	<1232302876.5803.32.camel@localhost> <49738A5A.7080704@waclawek.net>
Message-ID: <91705d080901181247j18f343bdh9664823054ac1527@mail.gmail.com>

On Sun, Jan 18, 2009 at 12:00 PM, Karl Waclawek <karl at waclawek.net> wrote:
> Daniel Leidert wrote:
>>
>> Am Sonntag, den 18.01.2009, 09:45 -0800 schrieb Dan Nicholson:
>>
>>>
>>> Just tried the build again on Linux x86 and x86_64. Everything seemed
>>> fine. I had a look at fedora and debian's expat packages. Here are
>>> some patches they're applying:
>>>
>>>
>>> http://cvs.fedora.redhat.com/viewvc/rpms/expat/devel/expat-1.95.8-pedantic.patch?view=markup
>>> http://patch-tracking.debian.net/package/expat/2.0.1-4
>>>
>>> I cc'd the package maintainers (at least, who I think they are), to
>>> see if they have any specific input on those patches.
>>>
>>
>> Of course I will do. I first mention the patch, followed by a short
>> explanation and the related Debian bug report (the same information can
>> also be found in the patch headers).
>>
>>
>> http://svn.debian.org/wsvn/debian-xml-sgml/packages/expat/trunk/debian/patches/82763_xmlwf_error_out_2.dpatch?op=file&rev=0&sc=0
>>
>> xmlwf exits with status zero in case of an error. It is common to error
>> out with a non-zero exit status. The patch simply makes the application
>> exit with status 2 in case of an error.
>> http://bugs.debian.org/82763
>>
>>
>
> Has this (and other issues) ever been reported to the Expat project on SF?
> For instance, from what I can tell, xmlwf returns non-zero for errors in
> quite a few cases (check the usage() calls, or XML_ProcessFile() in
> xmlfile.c.
>
> So I assume, we have a true bug here. This should be posted to
> https://sourceforge.net/tracker2/?atid=110127&group_id=10127
>
>>
>> http://svn.debian.org/wsvn/debian-xml-sgml/packages/expat/trunk/debian/patches/302191_install_expat_config_h.dpatch?op=file&rev=0&sc=0
>>
>> It seems, some projects (python-4suite) reference the expat_config.h
>> header file. The patch simply adds this file to be installed. I'm *not*
>> sure, that this patch should be accepted upstream. It might be an error
>> to reference expat_config.h in a software source. You should check (I
>> can do this too in a few days), why python-4suite references this header
>> file. Maybe moving some declarations to the installed header files is
>> the solution to go.
>> http://bugs.debian.org/302191
>>
>
> expat_config.h is generated for Unix, on Windows it does not exist. It
> should not generally be needed.

Looking at expat_config.h, I'd guess that an expat binding might want
to know these definitions:

/* Define to specify how much context to retain around the current parse
   point. */
#undef XML_CONTEXT_BYTES

/* Define to make parameter entity parsing functionality available. */
#undef XML_DTD

/* Define to make XML Namespaces functionality available. */
#undef XML_NS

But this is completely speculation, and I would hope that this
information would not be needed externally.

>> http://svn.debian.org/wsvn/debian-xml-sgml/packages/expat/trunk/debian/patches/342684_libtoolize.dpatch?op=file&rev=0&sc=0
>>
>> If you use some recent autotools, you can probably safely ignore this
>> patch. It simply runs the autotools chain on the source to get a newer
>> libtool version to support GNU/kFreeBSD.
>> http://bugs.debian.org/342684
>> http://bugs.debian.org/439127
>>
>
> Expat always seems to be behind on this area, but I have to leave this to
> our Unix experts.

Since the autotools are distributed with the tarball, it really kind
of depends on the person doing the release (you). Typically, you'd
want to do the release from wherever you have the most recent releases
of autoconf/automake/libtool. I don't know what platforms you do expat
development on, but any recent Linux distro would be fine.

Still, I wouldn't worry about this too much. Expat wouldn't be the
first or last package to need autotools updates. Distros know how to
manage this situation.

>> http://svn.debian.org/wsvn/debian-xml-sgml/packages/expat/trunk/debian/patches/412786_xmlwf_man_standard_fix.dpatch?op=file&rev=0&sc=0
>>
>> The SGML file contains a linebreak followed by three dots and and
>> parenthesis. The manual page contains the same linebreak. So the next
>> line in the manual page starts with the dots. But a leading dot has a
>> special meaning. GROFF expects a macro or request name after the dot. So
>> it throws a warning and doesn't print these four characters in the
>> resulting manual page. The patch simply removes the linebreak as an easy
>> solution to the problem.
>>
>> The second part of the patch removes a wrong statement in the BUGS
>> section. There you state, that the XML standard requires the XML
>> declaration for well-formedness. But that's not true. The declaration is
>> optional, as you can see here:
>> http://www.w3.org/TR/2006/REC-xml-20060816/#NT-prolog
>> http://bugs.debian.org/412786
>>
>
> Again, it would be nice to have this reported on the bug page. We do not
> normally Google for Expat bugs reported anywhere else.
> The SGML has not been updated since 2003. Who is actually using it? Anyway,
> a bug report would be useful, but also a review of the overall contents of
> the SGML file. Maybe we should discard it altogether?
>
>>
>> http://svn.debian.org/wsvn/debian-xml-sgml/packages/expat/trunk/debian/patches/485129_fix_underquotation_in_m4.dpatch?op=file&rev=0&sc=0
>>
>> In expat.m4 the AM_WITH_EXPAT macro is underquoted. See the paragraph
>> starting with "Starting with Automake 1.8, aclocal will warn about all
>> underquoted calls to AC_DEFUN [..]":
>> http://sources.redhat.com/automake/automake.html#Extending-aclocal
>> http://bugs.debian.org/485129
>>
>> The patch is trivial and safe.
>>
>
> Hope our build experts will do this.

This patch is definitely fine to commit.

--
Dan

From karl at waclawek.net  Sun Jan 18 22:31:03 2009
From: karl at waclawek.net (Karl Waclawek)
Date: Sun, 18 Jan 2009 16:31:03 -0500
Subject: [Expat-discuss] Time for a new release?
In-Reply-To: <91705d080901181247j18f343bdh9664823054ac1527@mail.gmail.com>
References: <91705d080901161153p3380307ax16ea7b94dc0deecc@mail.gmail.com>	
	<49722C87.6030104@waclawek.net>	
	<91705d080901171248p702857c0x88bbedf6de501d9@mail.gmail.com>	
	<49735284.8080904@waclawek.net>	
	<91705d080901180945h435f9475p60f9d7f6070ca904@mail.gmail.com>	
	<1232302876.5803.32.camel@localhost>
	<49738A5A.7080704@waclawek.net>
	<91705d080901181247j18f343bdh9664823054ac1527@mail.gmail.com>
Message-ID: <49739F97.7080404@waclawek.net>

Dan Nicholson wrote:
> Since the autotools are distributed with the tarball, it really kind
> of depends on the person doing the release (you). Typically, you'd
> want to do the release from wherever you have the most recent releases
> of autoconf/automake/libtool. I don't know what platforms you do expat
> development on, but any recent Linux distro would be fine.
>   

The issue here is that I only did the last release(s) because no-one 
else had the time.
I think everyone familiar with the Expat project  knows that my 
expertise is more with the code itself, and with Windows, if OS 
familiarity is required.
So I did my best - reading up on build knowledge as necessary, but I was 
also lucky that I didn't mess anything up.
> Still, I wouldn't worry about this too much. Expat wouldn't be the
> first or last package to need autotools updates. Distros know how to
> manage this situation.
>   
If anyone can recommend a recent - and safe - version of autotools, 
we'll see what I (or Fred) can do.

> In expat.m4 the AM_WITH_EXPAT macro is underquoted. See the paragraph
> starting with "Starting with Automake 1.8, aclocal will warn about all
> underquoted calls to AC_DEFUN [..]":
> http://sources.redhat.com/automake/automake.html#Extending-aclocal
> http://bugs.debian.org/485129
>
> The patch is trivial and safe.
>
>   
>> Hope our build experts will do this.
>>     
>
> This patch is definitely fine to commit.
>
>   
Applied in expat.m4 rev. 1.2.

Karl

From daniel.leidert.spam at gmx.net  Sun Jan 18 19:21:16 2009
From: daniel.leidert.spam at gmx.net (Daniel Leidert)
Date: Sun, 18 Jan 2009 19:21:16 +0100
Subject: [Expat-discuss] Time for a new release?
In-Reply-To: <91705d080901180945h435f9475p60f9d7f6070ca904@mail.gmail.com>
References: <91705d080901161153p3380307ax16ea7b94dc0deecc@mail.gmail.com>
	<49722C87.6030104@waclawek.net>
	<91705d080901171248p702857c0x88bbedf6de501d9@mail.gmail.com>
	<49735284.8080904@waclawek.net>
	<91705d080901180945h435f9475p60f9d7f6070ca904@mail.gmail.com>
Message-ID: <1232302876.5803.32.camel@localhost>

Am Sonntag, den 18.01.2009, 09:45 -0800 schrieb Dan Nicholson:
> On Sun, Jan 18, 2009 at 8:02 AM, Karl Waclawek <karl at waclawek.net> wrote:
> > Dan Nicholson wrote:
> >>
> >> Well, I wrote the pkg-config patch, and I'm involved in a lot of
> >> different projects helping with packaging. pkg-config is really
> >> helpful for another project that wants to depend on expat. A lot of
> >> Linux distros already ship an expat pkg-config file.
> >>
> >> I haven't tried to build expat from CVS in a while, but I don't recall
> >> there being any problems on Linux. I'll make sure that it still works,
> >> though, and send patches for anything wrong I see.
> >>
> >>
> >
> > OK, sounds good.
> 
> Just tried the build again on Linux x86 and x86_64. Everything seemed
> fine. I had a look at fedora and debian's expat packages. Here are
> some patches they're applying:
> 
> http://cvs.fedora.redhat.com/viewvc/rpms/expat/devel/expat-1.95.8-pedantic.patch?view=markup
> http://patch-tracking.debian.net/package/expat/2.0.1-4
> 
> I cc'd the package maintainers (at least, who I think they are), to
> see if they have any specific input on those patches.

Of course I will do. I first mention the patch, followed by a short
explanation and the related Debian bug report (the same information can
also be found in the patch headers).

http://svn.debian.org/wsvn/debian-xml-sgml/packages/expat/trunk/debian/patches/82763_xmlwf_error_out_2.dpatch?op=file&rev=0&sc=0

xmlwf exits with status zero in case of an error. It is common to error
out with a non-zero exit status. The patch simply makes the application
exit with status 2 in case of an error.
http://bugs.debian.org/82763

http://svn.debian.org/wsvn/debian-xml-sgml/packages/expat/trunk/debian/patches/302191_install_expat_config_h.dpatch?op=file&rev=0&sc=0

It seems, some projects (python-4suite) reference the expat_config.h
header file. The patch simply adds this file to be installed. I'm *not*
sure, that this patch should be accepted upstream. It might be an error
to reference expat_config.h in a software source. You should check (I
can do this too in a few days), why python-4suite references this header
file. Maybe moving some declarations to the installed header files is
the solution to go.
http://bugs.debian.org/302191

http://svn.debian.org/wsvn/debian-xml-sgml/packages/expat/trunk/debian/patches/342684_libtoolize.dpatch?op=file&rev=0&sc=0

If you use some recent autotools, you can probably safely ignore this
patch. It simply runs the autotools chain on the source to get a newer
libtool version to support GNU/kFreeBSD.
http://bugs.debian.org/342684
http://bugs.debian.org/439127

http://svn.debian.org/wsvn/debian-xml-sgml/packages/expat/trunk/debian/patches/412786_xmlwf_man_standard_fix.dpatch?op=file&rev=0&sc=0

The SGML file contains a linebreak followed by three dots and and
parenthesis. The manual page contains the same linebreak. So the next
line in the manual page starts with the dots. But a leading dot has a
special meaning. GROFF expects a macro or request name after the dot. So
it throws a warning and doesn't print these four characters in the
resulting manual page. The patch simply removes the linebreak as an easy
solution to the problem.

The second part of the patch removes a wrong statement in the BUGS
section. There you state, that the XML standard requires the XML
declaration for well-formedness. But that's not true. The declaration is
optional, as you can see here:
http://www.w3.org/TR/2006/REC-xml-20060816/#NT-prolog
http://bugs.debian.org/412786

http://svn.debian.org/wsvn/debian-xml-sgml/packages/expat/trunk/debian/patches/485129_fix_underquotation_in_m4.dpatch?op=file&rev=0&sc=0

In expat.m4 the AM_WITH_EXPAT macro is underquoted. See the paragraph
starting with "Starting with Automake 1.8, aclocal will warn about all
underquoted calls to AC_DEFUN [..]":
http://sources.redhat.com/automake/automake.html#Extending-aclocal
http://bugs.debian.org/485129

The patch is trivial and safe.



If you have any further questions or comments about the patches, please
don't hesitate to contact me.


PS: There is still an open bug report, you maybe want to comment/fix:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=245840
http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=23;bug=245840

Regards, Daniel


From daniel.leidert.spam at gmx.net  Sun Jan 18 21:32:21 2009
From: daniel.leidert.spam at gmx.net (Daniel Leidert)
Date: Sun, 18 Jan 2009 21:32:21 +0100
Subject: [Expat-discuss] Time for a new release?
In-Reply-To: <49738A5A.7080704@waclawek.net>
References: <91705d080901161153p3380307ax16ea7b94dc0deecc@mail.gmail.com>
	<49722C87.6030104@waclawek.net>
	<91705d080901171248p702857c0x88bbedf6de501d9@mail.gmail.com>
	<49735284.8080904@waclawek.net>
	<91705d080901180945h435f9475p60f9d7f6070ca904@mail.gmail.com>
	<1232302876.5803.32.camel@localhost>  <49738A5A.7080704@waclawek.net>
Message-ID: <1232310741.20348.4.camel@localhost>

Am Sonntag, den 18.01.2009, 15:00 -0500 schrieb Karl Waclawek:

[..]
> Has this (and other issues) ever been reported to the Expat project on SF?

I took over maintenance of this package last year. It seems, I missed to
report our reports/patches.

> For instance, from what I can tell, xmlwf returns non-zero for errors in 
> quite a few cases (check the usage() calls, or XML_ProcessFile() in 
> xmlfile.c.

Yeah, this might be true. I really just checked, if the patches are
valid, when I stepped into the maintainership.

[..]
> As a general comment, we would like bugs reported to the Expat project, 
> as we cannot go around hunting for bug reports elsewhere.

This is true and if you check even sf.net you will see, that I usually
report patches I apply for Debian.

Regards, Daniel


From jorton at redhat.com  Mon Jan 19 13:32:07 2009
From: jorton at redhat.com (Joe Orton)
Date: Mon, 19 Jan 2009 12:32:07 +0000
Subject: [Expat-discuss] Time for a new release?
In-Reply-To: <91705d080901180945h435f9475p60f9d7f6070ca904@mail.gmail.com>
References: <91705d080901161153p3380307ax16ea7b94dc0deecc@mail.gmail.com>
	<49722C87.6030104@waclawek.net>
	<91705d080901171248p702857c0x88bbedf6de501d9@mail.gmail.com>
	<49735284.8080904@waclawek.net>
	<91705d080901180945h435f9475p60f9d7f6070ca904@mail.gmail.com>
Message-ID: <20090119123207.GA6444@redhat.com>

On Sun, Jan 18, 2009 at 09:45:57AM -0800, Dan Nicholson wrote:
> Just tried the build again on Linux x86 and x86_64. Everything seemed
> fine. I had a look at fedora and debian's expat packages. Here are
> some patches they're applying:
> 
> http://cvs.fedora.redhat.com/viewvc/rpms/expat/devel/expat-1.95.8-pedantic.patch?view=markup
> http://patch-tracking.debian.net/package/expat/2.0.1-4
> 
> I cc'd the package maintainers (at least, who I think they are), to
> see if they have any specific input on those patches.

Thanks; I'm on the mailing list already.  I thought that the Fedora 
patch was already in CVS but it doesn't seem to be.  I've filed a bug 
with the patch:

https://sourceforge.net/tracker/index.php?func=detail&aid=2519651&group_id=10127&atid=110127

Regards, Joe

From alexcutovoi at gmail.com  Mon Jan 19 18:43:47 2009
From: alexcutovoi at gmail.com (Alex Cutovoi)
Date: Mon, 19 Jan 2009 15:43:47 -0200
Subject: [Expat-discuss] Compiling Expat to 64 bits
Message-ID: <c8378b160901190943r3f836dc3uf6d7701176cacdd@mail.gmail.com>

Hi for all

I've downloaded Expat and I would like to compile it to 64 bits version. I'm
using VC++ 2008 and I've converted the dsw to sln.
The project is being compiled with Batch Build option and in the properties
of the projects I setted the Debug and Release to 64 bits.
Now my doubts:
1) Some projects like "elements" in the Linker/Input option have this
dependencies: odbccp32, odbc32.lib. Do I need to change that libs to their
corresponding 64 bits?
2) I would like to create the libs. Is there are any additional steps?


Thanks for all replies



Alex

From karl at waclawek.net  Mon Jan 19 19:41:28 2009
From: karl at waclawek.net (Karl Waclawek)
Date: Mon, 19 Jan 2009 13:41:28 -0500
Subject: [Expat-discuss] Compiling Expat to 64 bits
In-Reply-To: <c8378b160901190943r3f836dc3uf6d7701176cacdd@mail.gmail.com>
References: <c8378b160901190943r3f836dc3uf6d7701176cacdd@mail.gmail.com>
Message-ID: <4974C958.60006@waclawek.net>

Alex Cutovoi wrote:
> Hi for all
>
> I've downloaded Expat and I would like to compile it to 64 bits version. I'm
> using VC++ 2008 and I've converted the dsw to sln.
> The project is being compiled with Batch Build option and in the properties
> of the projects I setted the Debug and Release to 64 bits.
> Now my doubts:
> 1) Some projects like "elements" in the Linker/Input option have this
> dependencies: odbccp32, odbc32.lib. Do I need to change that libs to their
> corresponding 64 bits?
>   

These dependencies should not be there. I have just committed updates to 
the project files that remove them.

> 2) I would like to create the libs. Is there are any additional steps?
>
>   
The static libs are built by the projects with "static" in their names.
I don't have access to a 64bit system. It would be nice if you could 
just give it a try and report back to us.

Karl

From weigelt at metux.de  Tue Jan 20 06:21:17 2009
From: weigelt at metux.de (Enrico Weigelt)
Date: Tue, 20 Jan 2009 06:21:17 +0100
Subject: [Expat-discuss] Time for a new release?
In-Reply-To: <49722C87.6030104@waclawek.net>
References: <91705d080901161153p3380307ax16ea7b94dc0deecc@mail.gmail.com>
	<49722C87.6030104@waclawek.net>
Message-ID: <20090120052116.GA19299@nibiru.local>

* Karl Waclawek <karl at waclawek.net> wrote:

Hi,

> The problem for me is, I am far from being a Unix/Linux build expert, so 
> I have no idea how important pkg-config is, and how to evaluate it.

vital.

> Unfortunately, we don't have anyone active on the Unix/Linux side right 
> now. Maybe Fred or Sebastian will pick up the torch.

I've already submitted patches years ago, and I really wonder 
why they haven't been applied yet ;-o


cu
-- 
---------------------------------------------------------------------
 Enrico Weigelt    ==   metux IT service - http://www.metux.de/
---------------------------------------------------------------------
 Please visit the OpenSource QM Taskforce:
 	http://wiki.metux.de/public/OpenSource_QM_Taskforce
 Patches / Fixes for a lot dozens of packages in dozens of versions:
	http://patches.metux.de/
---------------------------------------------------------------------

From weigelt at metux.de  Tue Jan 20 06:24:47 2009
From: weigelt at metux.de (Enrico Weigelt)
Date: Tue, 20 Jan 2009 06:24:47 +0100
Subject: [Expat-discuss] Time for a new release?
In-Reply-To: <49739F97.7080404@waclawek.net>
References: <91705d080901161153p3380307ax16ea7b94dc0deecc@mail.gmail.com>
	<49722C87.6030104@waclawek.net>
	<91705d080901171248p702857c0x88bbedf6de501d9@mail.gmail.com>
	<49735284.8080904@waclawek.net>
	<91705d080901180945h435f9475p60f9d7f6070ca904@mail.gmail.com>
	<1232302876.5803.32.camel@localhost>
	<49738A5A.7080704@waclawek.net>
	<91705d080901181247j18f343bdh9664823054ac1527@mail.gmail.com>
	<49739F97.7080404@waclawek.net>
Message-ID: <20090120052446.GB19299@nibiru.local>

* Karl Waclawek <karl at waclawek.net> wrote:

> If anyone can recommend a recent - and safe - version of autotools, 
> we'll see what I (or Fred) can do.

2.61 had been fine at my site for a long time.

BTW: mozilla's still stuck on very acient autoconf. They've ignored
my patches for now more than a year ;-O


cu
-- 
---------------------------------------------------------------------
 Enrico Weigelt    ==   metux IT service - http://www.metux.de/
---------------------------------------------------------------------
 Please visit the OpenSource QM Taskforce:
 	http://wiki.metux.de/public/OpenSource_QM_Taskforce
 Patches / Fixes for a lot dozens of packages in dozens of versions:
	http://patches.metux.de/
---------------------------------------------------------------------

From karl at waclawek.net  Tue Jan 20 16:15:19 2009
From: karl at waclawek.net (Karl Waclawek)
Date: Tue, 20 Jan 2009 10:15:19 -0500
Subject: [Expat-discuss] Time for a new release?
In-Reply-To: <20090120052116.GA19299@nibiru.local>
References: <91705d080901161153p3380307ax16ea7b94dc0deecc@mail.gmail.com>	<49722C87.6030104@waclawek.net>
	<20090120052116.GA19299@nibiru.local>
Message-ID: <4975EA87.30605@waclawek.net>

Enrico Weigelt wrote:
> I've already submitted patches years ago, and I really wonder 
> why they haven't been applied yet ;-o
>
>
>   


I don't see any open patches with your name.
Can you give me the patch numbers?

Karl