corresponding to ffx 3.5.x. Most patches taken from there, tested
successfully @ppc/amd64/sparc64. Branch 1.9.0.x is approaching attic
upstream, as ffx 3.0.x.
The plan is to move all users of xulrunner/1.8 to use this latest
version, and then ditch the old unmaintained one from ffx 2.x days.
Also change the configure style to 'gnu' instead of 'autoconf'
to avoid running autoconf twice (autoconf is run by the autogen.sh
script in the pre-configure target). landy@ says this fixes the
build on hppa for some reason.
ok aja, landry (for the configure-style bit some time ago)
to configure env so that it doesn't try to run tests that goes into an infinite
loop puking 'longjmp botch'. If anyone feels brave enough to debug that,
start in m4/sigaltstack*. That should allow quite a good branch of the
portstree to build again..
Glib now enforces threads requirement. As a result, this commit will
break p5-Glib2 (as our perl is not threaded).
Decision was taken after a chat with naddy@ and jasper@ as patching our
current glib2 like hell to cope with newer packages requirements is
clearly not a good solution.
naddy is ok with this move.
1.41. Tested without fallout in a bulk build by stephan@, thanks!
Endianess fixes from kili@, mark as NO_REGRESS as regression suite
changed a lot since old previous 1.34 version.
Remove deanna@ from MAINTAINER has she agreed not having time for it atm.
This port doesn't honour CFLAGS but this will be dealt separately.
Mox will make mock objects for you, so you don't have to create
your own! It mocks the public/protected interfaces of Python objects.
You set up your mock objects expected behavior using a domain
specific language (DSL), which makes it easy to use, understand,
and refactor!
This is required by newer GTK. We cannot just update Glib because it now
requires threads which will break p5-Glib2 dependent apps as our perl is
not threaded... solution to this is rthreads or ... <insert solution
here and send it to aja@>. Yes this means we are stuck with this version
for now.
