Hi, Trying this from trunk on a downstream package and of course as one expects all the existing builds break because includes are now wrong in building python extensions. It would be really handy if babel-config would tell us where it thinks all the babel stuff in python lives. E.g. Babel-config --query-var=LLNL_PYTHONINC should return (with the $ expanded appropriately already) "-I$PYTHONINC/llnl_babel -I$PYTHONINC/llnl_babel_sidl_sidlx" and whatever other babel related python Include directories may exist already or in future babels.
By the by, is there a reason to use llnl_babel_sidl instead of merely llnl_sidl? Thanks, Ben -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Adam C Powell IV Sent: Wednesday, September 24, 2008 11:53 AM To: Tom Epperly Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: Bug#493742: Conflict with python-babel On Tue, 2008-09-23 at 14:41 -0700, Tom Epperly wrote: > Adam C Powell IV wrote: > > Hi again, > > > > I know it's been a while... > > > > So to do this right, I'd just change 'setup(name="babel",' to > > 'setup(name="babel.sidl",' in setup.py and sidlsetup.py, right? > > > I am trying a "make distcheck" on the main trunk with the attached patch > (relative to the svn main trunk). This changes the name to "llnl_babel" > for sidlsetup.py and to "llnl_babel_<pkg1>_<pkg2>" for a Babel run that > produces code in packages pkg1 and pkg2. I think have a period in the > name might produce pain on some file systems. Great. I had just patched [sidl]setup.py and wondered why it didn't take... > By the way, I am still working on getting proper permission (in the form > of some kind of license) for the Babel documentation and its source. It > has been a chaotic year here due to our change in management. I understand, no worries. Neither the change in python package nor the documentation will be part of the upcoming 5.0 "Lenny" release (which froze in June), so there's no big rush. Thanks for taking the time to work with us on these two issues! Regards, -Adam -- GPG fingerprint: D54D 1AEE B11C CE9B A02B C5DD 526F 01E8 564E E4B6 Engineering consulting with open source tools http:// www. opennovation.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
