new build for mozilla-1.2 the gtk2 patch is still required i added a USE var to disable the composer this compiles runs and i built my new galeon-cvs ebuild http://bugs.gentoo.org/show_bug.cgi?id=11281 with it and it compiled and runs fine
Created attachment 6061 [details, diff] ebuild patch patch against mozilla-1.2_beta.ebuild
Created attachment 6062 [details, diff] ChangeLog patch
sorry guys it looks like this is broken it was working fine but i just restarted my gnome session and now its dying without getting to draw the window and no error message either i get this when i start it backgrounded from the command line [1]+ Exit 11 mozilla
Added a 1.2 ebuild to CVS.
just a couple of questions about this is there any reason why it requires gtk+2.1.2 ?? 1.2 beta built and ran fine with 2.0.? and any reason why you didnt mention the new USE option i added to disable the composer (some small credit would have been nice as well)
> is there any reason why it requires gtk+2.1.2 ?? > 1.2 beta built and ran fine with 2.0.? Part of the Xft2.0 testing we are doing. Guess I forgot that I tested it so, and missed it when commiting. > and any reason why you didnt mention the new USE option i added to disable the > composer It is most probebly due to me not looking at your ebuild. Yes, I know you did spent some time on this, sorry. Fact is just that I usually have a ebuild lying around that I already started hacking some time back ... do a diff against your version and mine, Im guessing it will be somewhat different. Also, if you can see there, I did not even mention adding the 'moznocompose' and 'mozcalendar' flags (which I see now is different to your 'moznocomposer'), but did add this bug # in the ChangeLog, thinking that it should be enouth if somebody wanted to track it back. If this is really an issue, Ill add to ChangeLog, just say the word. ChangeLog. If
> Part of the Xft2.0 testing we are doing. Guess I forgot that I tested it so, > and missed it when commiting. Ok, lets repeat this. We are doing a push for getting Xft2.0 into Gentoo. Currently it test fine, as Gnome2 works fine with unstable pango-1.1 and gtk+-2.1, and KDE 3.0.4 works fine with QT-3.1. Currently you have to disable Xft if using pango-1.0, so I cannot really see the use if using gtk+-2.0, as you get AA with galeon-1.2.7 anyhow with this ebuild (http://cvs.gentoo.org/~azarah/galeon-1.2.7.png). CVS galeon is anyhow much more unstable. I did however see that I still disable xft when gtk2 is in USE .. will fix.
ok thats cool dude i did change the gtk+ version to 2.0.? and did a build with your ebuild and it fell over when trying to find xft i am using gtk+2.0.9 i guess adding a disable xft if compiling with pango-1.0 would be a good idea then or its time to upgrade to gtk+2.1.?
Not yet. If you want to, you can unmask pango-1.1.3 and gtk+-2.1.2 and merge those. Also remember to unmask x11-libs/xft. Then you can help test it with us, and have nice AA fonts in galeon2 :) Relevant bug is at: http://bugs.gentoo.org/show_bug.cgi?id=10834
cool sounds fun to me dude will emerge gtk+2.1.2 and pango-1.1.3 and report my success on the bug you mentioned above
