lucene-pylucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bill Janssen <jans...@parc.com>
Subject Re: [VOTE] Release PyLucene 2.9.4-1 and 3.0.3-1 (take 2)
Date Fri, 10 Dec 2010 18:08:18 GMT
Andi Vajda <vajda@apache.org> wrote:

> >> I really want the latest up to date Mac OS X setup to build out of the
> >> box
> >
> > Sure, me too!
> 
> No, not today. Today's out of the box on 10.6 requires the setting to
> be under /Developer (without your patch).

Well, of course, that's why I sent you the patch :-).

> Downloading another Java package != out of the box. By out of the box,
> I mean current Xcode + whatever software update drops in on a regular
> basis, like the last Java update that lost the headers.

But what Apple is saying is that to install "current XCode" right now,
for Java, requires installing that extra download.  The current slogan
there is that being a Java developer on OS X requires "XCode plus
patches", apparently.

> >> ...and it seems that the current setup.py settings are the only way
> >> unless your patch get added ?

Of course, that will break on Lion when that's the latest and greatest.

> > My patch soft-codes the location of the SDK, so that it works with both
> > 10.5 and 10.6.  Though, after hearing from Swingler, I'd revise it as
> > follows (I just did this in Emacs, haven't tested it):
> 
> Ok then, provide a tested patch that works and applies out of the box
> to JCC's trunk, and that puts this code into a new helper file like is
> done for linux and windows (thus not adding pages of code to setup.py)
> and I'll integrate it.

OK, will do.  Wasn't sure about your feeling about it, or I would have
done it sooner.

> > Philosophically, I see little point in avoiding the use of an actual
> > programming language that using setup.py gives you.  Otherwise, might as
> > well use another Makefile.
> 
> You're not adressing the issue here: obscure automatic failures vs
> simple edits in setup.py to match your system.

Not going to touch that one... :-)

Bill

Mime
View raw message