Seamonkey 2.46 no longer includes ChatZilla
Our build adds a .desktop file for ChatZilla, which now results in an erroneous menu entry.
ChatZilla remains available as a plug-in.
Comments (13)
-
-
Do we want to upgrade SeaMonkey on 7.1, or leave it? After we discussed this in IRC, I realized that current ChatZilla users would still have it, as-is; the same as if they had installed the new SeaMonkey and installed ChatZilla from add-ons later, except with their settings already there.
-
reporter Tested new pkg in 7.2, looks good. 8 MB of space freed.
It removed the Chatzilla menu entry, I suspect cZ users would have to manually add the plug-in to recover that functionality. Still, Internet facing apps like browsers should be updated.
I just realized there is no menu entry for Composer, that would be nice to have. Should go in "Development".
-
reporter On the other hand... upgraded to 2.46 on my work computer, it borked my settings, hold off on any 7.1 updates.
-
reporter Test Two: Installed 7.2 Light B2 with SM 2.40 and configured a cZ profile. Upgraded to SM 2.46, then installed cZ add-on. It picked up right where it left off.
-
OK, looking at seamonkey-composer.desktop and linking icons from /usr/lib/seamonkey subdirs rather than keeping copies in the package's src directory.
-
SeaMonkey upgrade for 7.1 was discussed in IRC. It's not worthwhile to upgrade it while Firefox and -esr are also lagging behind.
-
The toolchain in 7.1 no longer allow us to update Firefox, so that will have to remain where it is. We may be able to update firefox-esr although not to the latest available.
As an alternative, I created a sub-project @ our gitlab a few days ago to see if re-packaging the binary version of FF would be an option for 7.1
These packages can be found here
I would be interested to know whether these work on 7.1 or not. These are just a re-package of what they provide in binary form.
-
Posting this from 7.1 Light, with ff 50.1.0. Installed your package above using upgradepkg --install-new. After starting and checking help > about for the version (50.0.2), it let me know a needed update was available and that I had to be root to go for it. Closed, started firefox from su, and now it's at 50.1. AFAICT, all my existing settings were picked up.
I won't be able to do further testing, as I'm busy with SeaMonkey. Your package is ready enough to ask select users on the forum to test it from where it is now.
If it goes to repos, put firefox in conflicts. Firefox 45 was not removed, but it cannot be started, even when accessing the previously linked "firefox-bin" directly. Even that starts the new version. May as well remove the now-extra, previous package. Warn potential testers, and eventually users.
Side note: Interrupted downloads of your file won't resume; they start over, whether using browser or "wget -c".
-
SeaMonkey progress:
I pushed changes to the seamonkey-rm-cz branch on my fork. Just an update, definitely won't build correctly just yet.
A paste of my to-do notes:
finish checking for patch disable
write new .desktops: suite, browser, mail, composer, address book, chat
disable chat .desktop for 2.46; copy to docs, leave note in sb
disable cz_sasl.js; provide a copy in docs
create FILES for docs
remove *.png, make links in pixmaps and hicolor to package-supplied icons
add gtk-update-icon-cache <hicolor> to doinst -
Plans right now are to distribute the new .desktops across categories so that the "Network" menu doesn't become huge; just browser and mail on that one, composer to dev . . .
-
Just merged pull request #86. Matches my to-do pretty well, but sasl script stays in awaiting plugin installation; didn't put FILES in doc, put seamonkey-chat.desktop there instead; icon cache rebuild was in the doinst already.
Either fixed a bug in 64-bit seamonkey-solibs, or created a brand new one. Let me know.
-
reporter - changed status to resolved
All issues solved in pkg built on 09 Jan 2017
- Log in to comment
Removed ChatZilla's SASL plugin references, the plugin's .js loader, the ChatZilla icon, and its .desktop. SeaMonkey package build is presently underway.