Re: Bug#615513: release.debian.org: armhf inclusion into the archive
On Wed, Jan 4, 2012 at 11:55 AM, David Given <firstname.lastname@example.org> wrote:
> Luke Kenneth Casson Leighton wrote:
>> ahh... webkit. do you have a system anywhere that has 2gb of RAM?
>> if not, i strongly strongly advise skipping the debug builds on any
>> webkit library.
> I'm running the prerelease Ubuntu precise on armhf. They have built
> webkit, but it just plain doesn't work: any web browser which uses it
> gets most of the way through rendering a page and then exits silently.
yeah you reallly have to use the builds that xan - carefully and
painstakingly - puts together, tests etc.
for midori ohh yeah that's webkitgtk-based - yeah, xan goes to a lot
of trouble to specifically patch the version of webkitgtk that he
releases, including patches that may not yet have been accepted into
webkit but are absolutely essential for stability.
> It *looks* suspiciously like the glib incompatibility described on the
> Midori FAQ page here:
> ...but of course the current glib version is much more recent that the
> ones mentioned.
i ran into an issue with libsoup in webkit 18 months ago - they did
some improvements that broke things... in webkit [with absolutely no
code-changes to webkit]. whoops. had to wait for the patches to make
their way through the system.
bottom line is: if you can get a set of "stake-in-ground" libraries
from anywhere, bloody well use them, don't arse about: there's too
much going on.
> I have no idea if any of this is relevant to Debian.
more than likely :)