On Sun, Feb 17, 2008 at 04:44:16PM -0800, Danek Duvall wrote:
> On Sun, Feb 17, 2008 at 02:50:20PM -0800, Nicolas Williams wrote:
>
> > Note that the version number of the libsqlite3 shared object comes from
> > SQLite3's build system; it is unclear what it ("0.8.6") means.
> >
> > +-------------------------------------+--------------+
> > | Filesystem object | Stability |
> > +-------------------------------------+--------------+
> > | | |
> > | /usr/bin/sqlite3 | Committed |
> > | /usr/lib/libsqlite3.so | Committed |
> > | /usr/lib/libsqlite3.so.0 | Uncommitted |
> > | /usr/lib/libsqlite3.so.0.8.6 | Uncommitted |
>
> What's the SONAME in the library? If it's just "libsqlite.so.0", then
> there's little point in shipping the .0.8.6 file at all. Conversely, if
> the SONAME is "libsqlite.so.0.8.6", then there's no point in shipping the
> .0 file.
It's "libsqlite3.so.0".
So I agree, I'll remove the .0.8.6 version.
> > | /usr/lib/pkgconfig/sqlite3.pc | Volatile |
>
> Why is this Volatile? It seems to me that the pkg-config module names are
> among the most stable of the interfaces in most opensource projects.
That's a mistake. It'll be Committed.
> Almost certainly more stable than the "0.8.6" in the library name, which I
> bet changes from release to release.
It doesn't, so far as I can tell.
