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

Bug#123100: ITP: openbabel -- Converter for chemical file formats

On Sun, Dec 09, 2001 at 08:47:40PM +0100, Michael Banck wrote:
> On Sun, Dec 09, 2001 at 08:03:55PM +0100, Ola Lundqvist wrote:
> > > Openbabel compiles and is useable, but no official release has been done
> > > yet. I will upload packages as soon as this happens.
> > 
> > Well if it is useable then you can upload it right now. 
> As it's a library (C++ even) I'm a bit hesitant to upload it now, with
> all the SO-name stuff one has to think of. Also, there are some issues
> with the datafiles I'm sorting out right now.

Ok I see.

> > But if a official release is very close you can wait some. 
> 'Early next year' according to the main developer...

Ok that sounds like you can wait some. On the other hand it might not
break that much until then. :)

> > If you have problems with the version 
> Hmm, the current version seems to be 2.0a1. Do you know if dpkg
> considers 2.0 to be greater than 2.0a1?

Well I'm not sure. Anyway you can add a x:version to the version
number to indicate that it really should be higher.


1:54-0 is higher than 0:99-0
0:4 is higher than 4.

> Actually, I could upload just the binary, statically compiled, so it
Why statically?

> gets into woody. Several packages mention babel in their description, so
> this might be worthwhile. The library can come later when the interfaces
> are settled. Note also that openbabel does not compile under gcc-3.0
> right now, although upstream promised to work on this next week.

Then you can wait.

> thanks for the suggestions,

No prob. :)


// Ola

> Michael

 --------------------- Ola Lundqvist ---------------------------
/  opal@debian.org                     Björnkärrsgatan 5 A.11   \
|  opal@lysator.liu.se                 584 36 LINKÖPING         |
|  +46 (0)13-17 69 83                  +46 (0)70-332 1551       |
|  http://www.opal.dhs.org             UIN/icq: 4912500         |
\  gpg/f.p.: 7090 A92B 18FE 7994 0C36  4FE4 18A1 B1CF 0FE5 3DD9 /

Reply to: