New galeon version has been out for quite a while with mozilla 1.5 support. Reproducible: Always Steps to Reproduce: 1. 2. 3.
does any of the gnome devs still have a gtk1 compiled mozilla, so he can test & update this ?
i managed to install it by just making a copy of the galeon-1.2.11.ebuild, naming it galeon-1.2.12.ebuild, editing it and changing the --with-mozilla-snapshot=${moz_ver}" variable to "--with-mozilla-snapshot=1.5b" and it works perfectly.
Mozilla 1.5 has been released into x86. Is there any chance of Galeon 1.2.12 also being put into Portage?
any dev who can check this... (someone with a muscular machine maybe) ?
ive just built a gtk1 mozilla, and will test and update this.
If you just build with --with-mozilla-snapshot 1.5 then it assumes this is == --with-mozilla-snapshot 1.4 (the MOZILLA_SNAPSHOT variable is set to 9 for both the 1.4 case, and the case where the version is not found). What does this mean? o For Mozilla 1.4 users Nothing, moz_ver will be set to 1.4 and should build fine o For Mozilla 1.5 users 1.5 will be incorrectly assumed to be 1.4, and cause build failure. What we need to do is add to the ebuild. [ $moz_ver == "1.5" ] && moz_ver="1.5b" Sound okay foser ? Works fine locally here (using mozilla 1.5).
i don't know, like another bug (don't have the no. handy) the version logic in the ebuilds is flawed it seems (?) I think we should write some working eclass function to handle this correctly instead of 'fixing' every other gecko based browser ebuild.
I tried this approach suggested in the last comment, and it works! I now have galeon 1.2 working again after mozilla 1.5 broke the old version. I noticed that this ebuild isn't even in the tree yet. I suggest that it be put there and made "stable" immediately because at this point in time NONE of the other versions work.
foser did you mean 33824 ? I know epiphany correctly identifies 1.5 as mozilla-1.5. This version of galeon however doesnt identify 1.5, and so guesses that it's an 'unknown version' which is equal to 1.4. I dont know the exact dates, but I think mozilla-1.5 went final after galeon-1.2.12 was released, which might explain it's absence from galeon. Can you elaborate a bit on the function ? I'm not opposed to that at all, but this version can't get in the tree until we finalise an eclass function, or 'patch/fix' the versioning in this version of galeon.
1.2.12 is in. Spider/hanno dealt with the same 1.5/1.5b situation in the development series, I expect it'll be fixed in the next 1.2 release, obsoleting the fix.
