|
|
Subject: Re: libdbd-sqlite-perl - msg#00033
List: linux.debian.devel.perl
On Mon, Dec 20, 2004 at 04:20:30PM +0100, Krzysztof Krzyzaniak wrote:
> > The changelog for 1.x doesn't actually mention something breaking,
> > so my guess is that the new DBD::SQLite is backwards compatible
> > and that
>
> it is not.
Just out of curiosity: how can a DBD not be backwards compatible? I
understand that the underlying engine might not be backwards
compatible. Do you perhaps mean that there are SQL statements that
SQLite 2 executed that SQLite 3 doesn't?
> > there's a libdbd-sqlite3-perl stuck in incoming's queue.
>
> No. There are prepared lidbd-sqlite2-perl packages but I have one
> problem. Generated .so file is not linked with any of sqlite package.
> I don't understand exactly how works xs packages of perl but I
> prepared this package with manually linked libsqlite0.
What do you mean "manually linked"?
It comes out fine here.
> When I fix problem with legacy package libdbd-sqlite2-perl package I'll
> upload libdbd-sqlite-perl compiled against sqlite3 libs.
Fine, but that doesn't really address the problem of existing programs
breaking, does it? What happens when both libdbd-sqlite2-perl and
libdbd-sqlite-perl are installed and one of these programs gets run?
Marcelo
Was this page helpful?
Thread at a glance:
Previous Message by Date:
click to view message preview
Re: libdbd-sqlite-perl
Dnia 20-12-2004, pon o godzinie 07:41 -0600, Marcelo E. Magallon
napisał(a):
> On Mon, Dec 20, 2004 at 11:54:46PM +1300, Nick Phillips wrote:
>
> > Seems that DBD::SQLite has now migrated to sqlite3, but that
> > libdbd-sqlite-perl has stayed at sqlite2 by actually packaging
> > DBD::SQLite2 rather than DBD::SQLite.
>
> Uhm... from README.Debian:
>
> Package name changes from DBD::SQLite to DBD::SQLite2.
>
> meaning the Perl package name, not the Debian package name.
>
> Upstream package DBD::SQLite >= 1.00 uses sqlite3. For compatibility
> reasons Debian use DBD-SQLite2 as foundation. Please, change in your
> programs connect param from "dbi:SQLite" to "dbi:SQLite2".
>
> Sounds broken to me. This means existing working programs will break
> in favor of future upstream compatibility. From upstream's changelog:
>
> 0.32
> - Renamed to DBD::SQLite2 to allow backwards compatibility
> - Implemented busy_timeout API
> - Add internal line number to error reporting
>
> The changelog for 1.x doesn't actually mention something breaking, so
> my guess is that the new DBD::SQLite is backwards compatible and that
it is not.
> there's a libdbd-sqlite3-perl stuck in incoming's queue.
No. There are prepared lidbd-sqlite2-perl packages but I have one
problem. Generated .so file is not linked with any of sqlite package. I
don't understand exactly how works xs packages of perl but I prepared
this package with manually linked libsqlite0.
"standard" package:
eloy@chlor:~$ ldd /usr/lib/perl5/auto/DBD/SQLite2/SQLite2.so
libc.so.6 => /lib/libc.so.6 (0x4005e000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x80000000)
"manually linked package"
eloy@chlor:~/tmp/perl/libdbd-sqlite2-perl-0.33/blib/arch/auto/DBD/SQLite2$ ldd
./SQLite2.so
libsqlite.so.0 => /usr/lib/libsqlite.so.0 (0x4005e000)
libc.so.6 => /lib/libc.so.6 (0x400b6000)
libpthread.so.0 => /lib/libpthread.so.0 (0x401ea000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x80000000)
If anyone could take look at packages from below and get response I'd be
happy:
deb http://kofeina.net/eloy/debian ./
When I fix problem with legacy package libdbd-sqlite2-perl package I'll
upload libdbd-sqlite-perl compiled against sqlite3 libs.
--
* Allegro.pl / Aukro.cz / Tetrako.hu
* Krzysztof 'eloy' Krzyżaniak
* <eloy@xxxxxxxxxx>
--
To UNSUBSCRIBE, email to debian-perl-REQUEST@xxxxxxxxxxxxxxxx
with a subject of "unsubscribe". Trouble? Contact listmaster@xxxxxxxxxxxxxxxx
Next Message by Date:
click to view message preview
unsubscribe shkelley1971@xxxxxxxxx
__________________________________
Do you Yahoo!?
Send a seasonal email greeting and help others. Do good.
http://celebrity.mail.yahoo.com
Previous Message by Thread:
click to view message preview
Re: libdbd-sqlite-perl
Dnia 20-12-2004, pon o godzinie 07:41 -0600, Marcelo E. Magallon
napisał(a):
> On Mon, Dec 20, 2004 at 11:54:46PM +1300, Nick Phillips wrote:
>
> > Seems that DBD::SQLite has now migrated to sqlite3, but that
> > libdbd-sqlite-perl has stayed at sqlite2 by actually packaging
> > DBD::SQLite2 rather than DBD::SQLite.
>
> Uhm... from README.Debian:
>
> Package name changes from DBD::SQLite to DBD::SQLite2.
>
> meaning the Perl package name, not the Debian package name.
>
> Upstream package DBD::SQLite >= 1.00 uses sqlite3. For compatibility
> reasons Debian use DBD-SQLite2 as foundation. Please, change in your
> programs connect param from "dbi:SQLite" to "dbi:SQLite2".
>
> Sounds broken to me. This means existing working programs will break
> in favor of future upstream compatibility. From upstream's changelog:
>
> 0.32
> - Renamed to DBD::SQLite2 to allow backwards compatibility
> - Implemented busy_timeout API
> - Add internal line number to error reporting
>
> The changelog for 1.x doesn't actually mention something breaking, so
> my guess is that the new DBD::SQLite is backwards compatible and that
it is not.
> there's a libdbd-sqlite3-perl stuck in incoming's queue.
No. There are prepared lidbd-sqlite2-perl packages but I have one
problem. Generated .so file is not linked with any of sqlite package. I
don't understand exactly how works xs packages of perl but I prepared
this package with manually linked libsqlite0.
"standard" package:
eloy@chlor:~$ ldd /usr/lib/perl5/auto/DBD/SQLite2/SQLite2.so
libc.so.6 => /lib/libc.so.6 (0x4005e000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x80000000)
"manually linked package"
eloy@chlor:~/tmp/perl/libdbd-sqlite2-perl-0.33/blib/arch/auto/DBD/SQLite2$ ldd
./SQLite2.so
libsqlite.so.0 => /usr/lib/libsqlite.so.0 (0x4005e000)
libc.so.6 => /lib/libc.so.6 (0x400b6000)
libpthread.so.0 => /lib/libpthread.so.0 (0x401ea000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x80000000)
If anyone could take look at packages from below and get response I'd be
happy:
deb http://kofeina.net/eloy/debian ./
When I fix problem with legacy package libdbd-sqlite2-perl package I'll
upload libdbd-sqlite-perl compiled against sqlite3 libs.
--
* Allegro.pl / Aukro.cz / Tetrako.hu
* Krzysztof 'eloy' Krzyżaniak
* <eloy@xxxxxxxxxx>
--
To UNSUBSCRIBE, email to debian-perl-REQUEST@xxxxxxxxxxxxxxxx
with a subject of "unsubscribe". Trouble? Contact listmaster@xxxxxxxxxxxxxxxx
Next Message by Thread:
click to view message preview
Re: libdbd-sqlite-perl
Dnia 20-12-2004, pon o godzinie 14:24 -0600, Marcelo E. Magallon
napisał(a):
> On Mon, Dec 20, 2004 at 04:20:30PM +0100, Krzysztof Krzyzaniak wrote:
>
> > > The changelog for 1.x doesn't actually mention something breaking,
> > > so my guess is that the new DBD::SQLite is backwards compatible
> > > and that
> >
> > it is not.
>
> Just out of curiosity: how can a DBD not be backwards compatible? I
> understand that the underlying engine might not be backwards
> compatible. Do you perhaps mean that there are SQL statements that
> SQLite 2 executed that SQLite 3 doesn't?
I mean you cannot use you database files created with sqlite2 with new
DBD::SQLite
package.
> > > there's a libdbd-sqlite3-perl stuck in incoming's queue.
> >
> > No. There are prepared lidbd-sqlite2-perl packages but I have one
> > problem. Generated .so file is not linked with any of sqlite package.
> > I don't understand exactly how works xs packages of perl but I
> > prepared this package with manually linked libsqlite0.
>
> What do you mean "manually linked"?
I mean adding in Makefile.PL of lidbd-sqlite2-perl
'LIBS' => "-lsqlite",
and
'LIBS' => "-lsqlite3",
in libdbd-sqlite3-perl package.
> It comes out fine here.
>
> > When I fix problem with legacy package libdbd-sqlite2-perl package I'll
> > upload libdbd-sqlite-perl compiled against sqlite3 libs.
>
> Fine, but that doesn't really address the problem of existing programs
> breaking, does it? What happens when both libdbd-sqlite2-perl and
> libdbd-sqlite-perl are installed and one of these programs gets run?
Should be no problem with that. But I haven't test heavily that because
I don't have any sqlite3 databases yet (except testing one).
eloy
--
* Allegro.pl / Aukro.cz / Tetrako.hu
* Krzysztof 'eloy' Krzyżaniak
* <eloy@xxxxxxxxxx>
--
To UNSUBSCRIBE, email to debian-perl-REQUEST@xxxxxxxxxxxxxxxx
with a subject of "unsubscribe". Trouble? Contact listmaster@xxxxxxxxxxxxxxxx
|
|