![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Would it be possible to update the libtool used when building the release tarballs to something newer than 1.4.3? |
#3
| |||
| |||
|
|
Andres Salomon wrote: Would it be possible to update the libtool used when building the release tarballs to something newer than 1.4.3? It would be difficult. I have machines with newer libtools, but other things are broken about them, such as doxygen. And for compatibility reasons, I can't just upgrade libtools on the older machine I build the source tarball on. |
#4
| |||
| |||
|
|
Ok. Well, I guess as long as you're aware that the libtool being used is out of date. I can easily update the libtool stuff for debian packages, but I was hoping to get it updated upstream so I wouldn't potentially forget every time I packaged up a new release. |
#5
| |||
| |||
|
|
On Thu, Sep 15, 2005 at 01:11:34AM -0400, Andres Salomon wrote: Ok. Well, I guess as long as you're aware that the libtool being used is out of date. I can easily update the libtool stuff for debian packages, but I was hoping to get it updated upstream so I wouldn't potentially forget every time I packaged up a new release. Is mysql++ going into Debian officially? This would be excellent. Gentoo is the only distro to have it officially.... at least that I know of. A quick search tells me they have 2.0.4 in portage already, as an unstable ebuild, which is cool. - Chris |
#6
| |||
| |||
|
|
I'm not sure why the decision was made to call it libsqlplus |
|
if anyone has a better suggestion than libmysql++ or libmysqlplusplus, let me know. I'm also considering libmysqlpp. |
![]() |
| Thread Tools | |
| Display Modes | |
| |