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
Message-ID: <018d01c2f255$4dae5d90$ab474e51@ellixia>
From: "Elfyn McBratney" <elfyn AT exposure DOT org DOT uk>
To: "cygwin" <cygwin AT cygwin DOT com>, "Robert Collins" <rbcollins AT cygwin DOT com>
References: <3E7EF6E0 DOT 70401 AT fillmore-labs DOT com> <1048508508 DOT 905 DOT 134 DOT camel AT localhost> <001101c2f209$d5308730$ab474e51 AT ellixia> <1048542436 DOT 912 DOT 158 DOT camel AT localhost>
Subject: Re: xsltproc segfaults after upgrading to docbook xslstylesheetsv1.60.1
Date: Mon, 24 Mar 2003 22:32:50 -0000
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300

> 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).
> * 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.

Will do. Thanks for the tips.. :-)

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

Typo. I meant to say "these are packages"...

> 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).

Sorry, Didn't mean to make it sound like you abbandoned it.

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

Funny you said that. I was actually going to reply to Patrick and comment on
his harshness, and if it wasn't for the fact that I was late for work I
would have done...I see Larry beat me to it. If it wasn't for you
maintaining the originals I/someone else would have to cover a lot of new
ground, so offering to help seemed a h**l of a lot better than bitching and
not doing anything to rectify the situation

> Rob


Regards,

Elfyn McBratney
elfyn AT exposure DOT org DOT uk
www.exposure.org.uk



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/