[Frugalware-devel] seamonkey 2.0
ryuo at frugalware.org
Mon Nov 30 12:41:32 CET 2009
> On Sun, Nov 29, 2009 at 10:16:57PM -0600, James Buren
> <ryuo at frugalware.org> wrote:
>> I'm working on upgrading seamonkey to 2.0. While working on it, it
>> complains that our libpng does not have APNG support. I dug deeper and
>> found this is a feature provided by a patch to libpng for "animation
> Same here - any reason that patch is not in upstream?
>> Arch uses it by default to their libpng. Do you think its worth
>> patching our libpng so this can be used in a shared library rather than
>> using the static library provided with the sources of seamonkey?
> This is a separate issue, right? The question here is who will maintain
> the patch. The problem is that once you make it a shared library, you
> have to care about API changes, upstream provides a static lib only in
> several cases to be able to ignore this problem, since obviously static
> libs doesn't have any SO numbers.
> So just building it as a shared lib named ".so.0" does not make too much
> sense, while deciding when to bump the number isn't a trivial task. Are
> you aware of this?
Oh. I haven't had to deal with shared library problems before, so please
excuse my ignorance.
> Frugalware-devel mailing list
> Frugalware-devel at frugalware.org
More information about the Frugalware-devel