--- "Mike C. Fletcher" <mcfletch@...> wrote: >
Rene Dudfield wrote:
> >I'm going to add some of the recently submitted
> >patches tonight. This ok?
> Yup, hopefully nothing that'll break the tree, of
> course :) . I'll run
> through the whole suite of tests with OpenGLContext
> tomorrow before I
> sit down to do the release.
I'll add the patches, do the tests, get a friend with
rh8 to test as well.
I forgot to ask about the tcl empty redraw function?
Are there any problems with adding this?
> >I added a check for swig 1.3.13, but it exits even
> >though swig doesn't need to be built. I'll remove
> >that check until I figure out how to get the
> >check working for a source release(ie swig is not
> >being used, so don't do the check). I think the
> >distutils works, it may be to hard to do this.
> >Instead maybe a warning should be printed( print
> >swig 1.3.13";time.sleep(5))
> Distutils, unfortunately, is a really annoying beast
> to understand the
> topology of. If I'm not mistaken there's lots of
> places where a check
> can be added that simply marks the build command
> un-accomplishable. I
> think the doc-building command uses this somewhere
> to disallow building
> if there's no saxon processor available.
> >Do you just do 'python setup.py sdist' to make the
> >source release?
> It's actually:
> python setup.py sdist --force
> But because of the linux permission/line-feed
> problems I'm considering
> only doing .zip on the windows machine and doing the
> gztar on a linux
> machine (same machine, of course ;) ) tomorrow,
> hopefully having CVS
> handle all of the line-feed issues.
> >The other thing we need to do is figure out the
> >feed problems. Maybe a s/\r\n/\n/ at the end of it
> >all would be a good test? To print as warnings
> >containing them, or optionally fixing up those
> To be quite frank, I'm surprised that this is
> causing problems. Either
> _every_ C/C++ extension packaged with distutils is
> going to cause a
> problem or one of our disutils customisations is
> cocking up. I'd like
> to find out which piece of our customisation is the
> problem and fix
> that, rather than adding a hack later on.
Ok. I might add this as a test at the end. To print
warnings about those files.
> Night all,
> > --- "Mike C. Fletcher" <mcfletch@...>
> wrote: >
> >If there's anything you developers need in the next
> >>alpha release, get
> >>it in quick-like. Will do a source release
> >>tomorrow, and possibly try
> >>booting up RedHat 8 to do a binary release.
> >>This won't have many changes, just the
> >>texture-compression extension fix
> >>and the GLU tessellator-callback fix AFAI can
> >>Enjoy all,
Do You Yahoo!?
Everything you'll ever need on one web page
from News and Sport to Email and Music Charts