Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Subject: Re: xsltproc segfaults after upgrading to docbook xsl
	stylesheetsv1.60.1
From: Robert Collins <rbcollins AT cygwin DOT com>
To: Elfyn McBratney <elfyn AT exposure DOT org DOT uk>
Cc: cygwin <cygwin AT cygwin DOT com>
In-Reply-To: <001101c2f209$d5308730$ab474e51@ellixia>
References: <3E7EF6E0 DOT 70401 AT fillmore-labs DOT com>
	 <1048508508 DOT 905 DOT 134 DOT camel AT localhost>
	 <001101c2f209$d5308730$ab474e51 AT ellixia>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-TbOBqF7guklWDLpDO7h+"
Organization: 
Message-Id: <1048542436.912.158.camel@localhost>
Mime-Version: 1.0
Date: 25 Mar 2003 08:47:17 +1100

--=-TbOBqF7guklWDLpDO7h+
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Tue, 2003-03-25 at 00:32, Elfyn McBratney wrote:
> Robert,
>=20
> I started working on this one last night. Now I know what you mean by the=
se
> packages being a bugger to build OOTB. In the coming week I'm going to be
> testing this and release a test package for people to try, if you don't m=
ind
> of course. :-)

I don't mind one iota. I do suggest you leverage the -src package for
the currently-on-cygwin.com packages. Strip out the autoconf generated
file patches, and you'll see what has to be forward ported. Some of the
stuff may be eligible (now) for pushing upstream, but the bulk won't be,
unless I've missed a transition to automake 1.5+ (which I *don't think)
I have.

Specific things to watch for:
* python bindings (new in the cygwin package, more stable in upstream
now).
* new exports from dynamic libraries (I check for new exports via the
win32 .dll specs, and ensure they are libtool auto-import compatible).=20
* libtool API interface changes. If the interface has changed in a
backwards compatible way, when you link xsltproc, xmllint etc, you'll
link against your installed version which may not have enough symbols to
link successfully. Secondly if the interface has brokne backwards
compatability, but the libtool library identifier hasn't been bumped,
well, welcome to h**l.
* per object flags are needed to prevent duplicate or missing symbols
against libxml and the test programs in libxml.

Ask me if you get other surprises, I may have forgotten something.

> As for maintainership I volunteer, as this is a package I don't want to s=
ee
> pulled from the distribution.

Thank you. I stepped down because I realised I wasn't fulfilling my
obligations and simply didn't want to get whipped to devote time I don't
have, on someone elses schedule, not because I wanted to see the package
removed (I don't).

What I find ironic is the immediate offer to help that you recieved,
rather than abuse.

Rob

--=20
GPG key available at: <http://users.bigpond.net.au/robertc/keys.txt>.

--=-TbOBqF7guklWDLpDO7h+
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQA+f3zkI5+kQ8LJcoIRArfzAJ9JunzraEyaFB6ote/NeieL7RiNAgCgl+6W
46q8IQgUjCiwQ3SFTZFlYGw=
=RA+0
-----END PGP SIGNATURE-----

--=-TbOBqF7guklWDLpDO7h+--