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
X-Authentication-Warning: eos.vss.fsi.com: ford owned process doing -bs
Date: Thu, 10 Jul 2003 15:43:50 -0500 (CDT)
From: Brian Ford <ford AT vss DOT fsi DOT com>
X-X-Sender: ford AT eos
To: cygwin AT cygwin DOT com
Subject: Re: development under 1.5.0 ?s
In-Reply-To: <Pine.GSO.4.44.0307101628390.6088-100000@slinky.cs.nyu.edu>
Message-ID: <Pine.GSO.4.56.0307101535150.1846@eos>
References: <Pine DOT GSO DOT 4 DOT 44 DOT 0307101628390 DOT 6088-100000 AT slinky DOT cs DOT nyu DOT edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Thu, 10 Jul 2003, Igor Pechtchanski wrote:

> On Thu, 10 Jul 2003, Brian Ford wrote:
>
> > Yeah, that's what I thought.  I was hopping we might have figured out an
> > easy way to do this by now, though.  Oh, well.  I'll figure it out myself.
> >
> > One reason I ask is that I am the unofficial lesstif maintainer, and I
> > need to figure out when it is safe to build the new lesstif libs.
>
> If you use no other DLLs, you can simply recompile the lesstif DLLs and
> release them in a test package.  Otherwise, check the prototypes of the
> functions your DLLs call to see if they contain any of the changed
> datatypes (see Chris's reply), perhaps recursively in structs.  If not,
> you can use them.
>
I just checked, and lesstif only depends on the Xlibs.  I haven't checked
yet, and don't plan to (that's a huge job!), if any of the Xlib
interfaces use any of the types that changed sizes, however.

So, being the conscientious package maintainer that I am, do I go ahead and
release a new test lesstif package before the Xlibs have been recompiled,
or do I wait?

lesstif should come out the same regardless.  But depending on
the types used in the Xlib interfaces, my new lesstif test package may be
broken until a new Xlib test package is installed and released.

Do I have this right?

-- 
Brian Ford
Senior Realtime Software Engineer
VITAL - Visual Simulation Systems
FlightSafety International
Phone: 314-551-8460
Fax:   314-551-8444

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/