Add linux-specific improvements from the swift-projects at http://swiftweasel.tuxfamily.org/ This could be done with an additional useflag, like "iceweasel" in firefox.
Created attachment 192588 [details, diff] Example patch for swiftweasel First try to patch mozilla-firefox-ebuild for swiftweasel
Created attachment 192590 [details, diff] Example patch for swiftdove First try to patch mozilla-thunderbird-ebuild for swiftdove.
really interesting, but website is a bit empty....
This should be a different package...
(In reply to comment #4) > This should be a different package... > And why? You can't just change the summary without giving any reason. The reasons why I mentioned the use-flag where: 1) Swiftweasel's source code is provided as patch to Firefox' source code. (Swiftdove similar 2) iceweasel is already handled via use-flag; it would be more consistent if swiftweasel is too
(In reply to comment #5) > (In reply to comment #4) > > This should be a different package... > > > > And why? You can't just change the summary without giving any reason. > > The reasons why I mentioned the use-flag where: > 1) Swiftweasel's source code is provided as patch to Firefox' source code. > (Swiftdove similar > 2) iceweasel is already handled via use-flag; it would be more consistent if > swiftweasel is too > 1) I gave a reason 2) I'm in the mozilla team and i think this should be a new package(where the mozilla herd is not going to maintain it) 3) The iceweasel USE-flag just changes the icons and the name of the application, there's no patching.
I, too, think that an useflag is the better solution. It would certainly be easier to implement and maintain than a new package. I understand your concerns that the Swiftweasel optimizations are not maintained by the Mozilla team though.On the other hand, unsupported useflags already exist (custom-cflags for instance) There already is a "custom-optimization" useflag, maybe we could use that and tell the user that it's not supported in postinst?
I personally oppose a USE flag for firefox, because: * I want to have both browsers installed at once * swiftfox lags behind firefox releases. portage will want to install new firefox releases when the swiftfox version for that release isn't even available. so portage will install firefox without the swiftfox modifications unless you're careful and make sure it has the 'swiftfox' USE flag. and once the ebuild is finally updated with the swiftfox modificaions, you'll have to specify --newuse just to get it. I think it it's less complicated to just make a new ebuild.
by the way, something has changed in the firefox ebuild since you made the patch, I think: localhost ~ # patch /usr/portage/www-client/mozilla-firefox/mozilla-firefox-3.0.10.ebuild swiftweasel.diff -o swiftfox.ebuild patching file /usr/portage/www-client/mozilla-firefox/mozilla-firefox-3.0.10.ebuild Hunk #1 FAILED at 18. Hunk #2 FAILED at 92. Hunk #3 FAILED at 111. Hunk #4 FAILED at 181. Hunk #5 FAILED at 246. 5 out of 5 hunks FAILED -- saving rejects to file swiftfox.ebuild.rej
Mozilla team will not pick this up, if an individual maintainer steps up and wants to place it under the mozilla herd that would be acceptable. I see no reason for swiftweasel we already have icecat which is the same ideal.
(In reply to comment #10) > Mozilla team will not pick this up, if an individual maintainer steps up and > wants to place it under the mozilla herd that would be acceptable. I see no > reason for swiftweasel we already have icecat which is the same ideal. > we already have openoffice, but koffice is the same ideal, eh?
(In reply to comment #10) > Mozilla team will not pick this up, if an individual maintainer steps up and > wants to place it under the mozilla herd that would be acceptable. I see no > reason for swiftweasel we already have icecat which is the same ideal. > further, icecat and swiftweasle are not the same ideal. icecat: "Its main advantage is an ethical one," it is a rebranding of firefox, removing all trademarked things from it. it also has some other privacy features added. it is not intended to be faster than firefox. swiftweasle: "Swiftweasel is an optimized build of the Mozilla Firefox web browser for Linux," it's intended purpose is to be fast. as far as I can tell, it should even be possible to merge icecat's firefox changes (removal of trademarked stuff and some pllugins) into swiftweasle.
Created attachment 225361 [details, diff] swiftweasel patch for firefox 3.5.6 download the following files from portage archive: http://sources.gentoo.org/viewcvs.py/*checkout*/gentoo-x86/www-client/mozilla-firefox/files/firefox-default-prefs.js http://sources.gentoo.org/viewcvs.py/*checkout*/gentoo-x86/www-client/mozilla-firefox/files/000_flex-configure-LANG.patch http://sources.gentoo.org/viewcvs.py/*checkout*/gentoo-x86/www-client/mozilla-firefox/mozilla-firefox-3.5.6.ebuild slap them in the right place, apply the patch against the ebuild, digest, and emerge with "swiftweasel" USE flag. viola. you now have swift fox version 3.5.6 (the latest as of this posting) my changes in the patch were made so that when a newer version of swiftfox is released, you can simply rename the ebuild to that version and it should emerge just fine (theoretically)
eh, more specifically, cd /usr/portage/www-client/mozilla-firefox # or make your own overlay patch mozilla-firefox-3.5.6.ebuild /home/user/mozilla-firefox-3.5.6-r1.patch -o mozilla-firefox-3.5.6-r1.patch echo ">mozilla-firefox-3.5.6-r1" >> /etc/portage/packages.mask/firefox-for-swiftfox
