[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#461087: python-babel: package name conflict?



On Thu, 2008-08-07 at 00:28 +0200, Christoph Haas wrote:
> On Donnerstag, 7. August 2008, Adam C Powell IV wrote:
> > Okay.  Before writing upstream, "dpkg -L python-babel" shows everything
> > in site-packages/sidl[x].  Is there a way I can change my EGG-INFO to
> > SIDL instead of Babel?  Or would that break everything using it (which
> > is nothing now, at least no Debian packages)?
> 
> IMHO you would have to alter the setup.py. The setuptools are creating the 
> EGG-INFO directory automatically. Might be better to have the upstream do 
> this. setuptools can be beasty.

If that's it, it's easy.  "babel" or "Babel" only appears once in
setup.py: "setup(name='babel',".

Grepping -i through all of the python source, babel only appears in
printfs, comments, a couple of #include "babel_config.h", the one spot
above, and another like it in sidlsetup.py.  It seems like it wouldn't
be such a bad thing to just change it...

Yes, my package was in sarge, but that was pre-1.0, and python-babel
didn't work then.  So I don't think there's a significant user community
for this in Debian -- yet.

> > On Thu, 2008-08-07 at 00:05 +0200, Christoph Haas wrote:
> > > What a waste of time... :)
> >
> > Not necessarily -- if it lets people internationalize SIDL programs, or
> > at least install their dependencies simultaneously...
> 
> Yes, we need to sort this out. I mean the whole issue that the upstreams 
> have conflicts in their egg names.

Ah, yes.  Good point.

-Adam
-- 
GPG fingerprint: D54D 1AEE B11C CE9B A02B  C5DD 526F 01E8 564E E4B6

Engineering consulting with open source tools
http://www.opennovation.com/

Attachment: signature.asc
Description: This is a digitally signed message part


Reply to: