Re: libphysfs 1.0.1

[Adeodato Simó <dato@net.com.org.es>]

* Barry deFreese [Tue, 10 Mar 2009 14:50:26 -0400]:

> OK, checking with nm -D for __PHYSFS, I get the following:

> libparagui1.1 - No results for __PHYSFS.  Builds fine with libphysfs-1.1.1.
> asc - No result for __PHYSFS.  Builds fine with libphysfs-1.1.1 and  
> libparagui1.1 built with libphysfs-1.1.
> balder2d - No results for __PHYSFS.  Builds fine with libphysfs-1.1.1.
> lincity-ng - No results for __PHYSFS.  Builds fine with libphysfs-1.1.1.
> netpanzer - No results for __PHYSFS.  Builds fine with libphysfs-1.1.1.
> pingus - No PHYSFS at all.  Looks like a spurious build-dep.  Upstream  
> seems to have removed it some time in 2007.
> tmw - No results for __PHYSFS.  Builds fine with libphysfs-1.1.1.
> trigger-rally (trigger) - No results for __PHYSFS.  Builds fine with  
> libphysfs-1.1.1.
> warzone2100 - No results for __PHYSFS.  Builds fine with libphysfs-1.1.1.

Great! Were the nm checks for __PHYSFS done after or before the rebuild?
I ask because this:

> love - Currently FTBFS. Unrelated.

Do the current packages have any __PHYSFS symbols?

> taoframework -

What about this one?

> Does that help any?

Yes! So, if the checks for __PHYSFS_* symbols were done before the
rebuild, this means there is no need to bump the SONAME.

So, since that's cleared up, only communication with upstream is left.
I'll contact you on IRC about this.

Cheers,

-- 
- Are you sure we're good?
- Always.
        -- Rory and Lorelai