Wary: SeaMonkey 2.12.1

I have started to look at getting Wary and Racy organised for the next release.

I was unable to compile SeaMonkey 2.12.1. It required upgrading of libvpx (from 0.9.7 to 1.1.0) and sqlite (from 3.7.10 to 3.7.14), however it seems that the version of gcc in Wary is too old. I did some research on this, fiddled around for sometime, but was unable to compile SM.

So, I used the official binary from the SM website, made it into a PET. This requires 'dbus-glib', so I enabled that (and 'dbus') in the Wary (and Racy) package-list.
Note, it does not use the system libvpx and sqlite, has it's own inbuilt. Ditto for cairo.

As this new PET includes the IRC-chat client module, I added a menu entry under the 'Internet' category.

Sigh... I don't like to see this. Just looking at the SM PETs, version 1.1.19 is 10.1MB, 2.0.11 is 11.2MB, and 2.12.1 is 21.5MB!

The PETs (252KB, 307KB, 21.5MB, 380KB, 443KB):
http://distro.ibiblio.org/quirky/pet_packages-wary5/libvpx-1.1.0-w5c.pet
http://distro.ibiblio.org/quirky/pet_packages-wary5/libvpx_DEV-1.1.0-w5c.pet
http://distro.ibiblio.org/quirky/pet_packages-wary5/seamonkey-2.12.1-x86.pet
http://distro.ibiblio.org/quirky/pet_packages-wary5/sqlite-3.7.14-w5c.pet
http://distro.ibiblio.org/quirky/pet_packages-wary5/sqlite_DEV-3.7.14-w5c.pet


Posted on 24 Sep 2012, 10:16


Comments:

Posted on 24 Sep 2012, 12:48 by Dewbie
SeaMonkey 1.1.19
I'm curious about something, Barry:

You used SeaMonkey 1.1.18, instead of 1.1.19, with Wary 5.1.2 to 5.1.4.1.

Were there any problems with 1.1.19?
Thanks.


Posted on 24 Sep 2012, 12:53 by Dewbie
SeaMonkey 2.x fonts
Also, fonts in the more recent SeaMonkey 2.x builds are rough on the eyes. Here's a thread with a solution: http://www.murga-linux.com/puppy/viewtopic.php?p=654167#654167


Posted on 24 Sep 2012, 13:16 by Ramacahndran
Wary/Racy
Dear Sir

Also provided Iron browser pet package for Wary or Racy. While trying to install Iron or Google Chrome in Racy/Wary, it is asking many dependency files. Please provide Chromium Browser with all dependency file or only separate dependency Pet package required for installing Chrome build browser in Racy or Wary.


Posted on 24 Sep 2012, 13:39 by technosaurus
seamonkey + nobus
I am currently running the official build with the nobus pet I posted in the Racy thread here:
http://murga-linux.com/puppy/viewtopic.php?p=653918#653918
the pet seems to be working OK, but I can patch it fairly simply if we find any problems. It will be nice to be able to use dbus/dbus-glib official apps ootb for only 17kb


Posted on 24 Sep 2012, 17:03 by BarryK
Re SM 1.1.18
Dewbie,
I seem to recall, I was able to get 1.1.18 extra small. I don't recall the details, but I don't think that I was able to get 1.1.19 that small.

My SM 1.1.18 PET is only 9.1MB.



Posted on 24 Sep 2012, 17:12 by BarryK
Re SM 2.x fonts
Dewbie wrote:

Edit / Preferences / Appearance / Fonts will allow changes to webpage fonts, but not URL and toolbar fonts.
Does anyone know how to do this?
The letter spacing is so tight that the URLs are almost unreadable.


I don't have this problem. Running SM 2.12.1 in Wary right now, the URL box is using DejaVu Sans and looks good.

This is because the SM PETs that I create have /root/.mozilla/.../userChrome.css, that specifies DejaVu Sans 12-pixel font for URL-box etc.



Posted on 24 Sep 2012, 17:22 by BarryK
Re nobus
technosaurus,
Very interesting!

The nobus site states that nobus is a compile-time thing, should be installed before an app such as SM is compiled.

But, you are saying that the already-compiled official SM binary works with nobus?

if that is the case, it might be a good choice for Wary. But, I have been wondering about that. My dbus PET is somewhat emasculated anyway, and doesn't seem to slow anything down. If there is any app that wants dbus and does actually need a functional dbus daemon, then it won't be happy with nobus.

So... maybe I should just go for having my dbus and dbus-glib PETs in Wary and Racy.



Posted on 24 Sep 2012, 18:40 by Dewbie
Re SM 2.x fonts
BarryK wrote:
I don't have this problem. Running SM 2.12.1 in Wary right now, the URL box is using DejaVu Sans and looks good.

This is because the SM PETs that I create have /root/.mozilla/.../userChrome.css, that specifies DejaVu Sans 12-pixel font for URL-box etc.


Ahhh...I'm running an official SM build of 2.12.1., in Puppy Linux 4.1.2.

Never had a fonts problem with SM 1.x official builds. So much for progress.


Posted on 25 Sep 2012, 10:37 by Dewbie
Update
OK, did some testing and updated that thread.
(See link above, in previous post.)


Posted on 25 Sep 2012, 12:45 by session
Official SM is slower
Official builds are certainly clunkier on my older PC; I thought it may be dbus--performance with nobus confirms that to a tiny degree, it is--but it's mainly a vanilla build thing... sigh...


Posted on 25 Sep 2012, 13:25 by disciple
Re nobus
> Re nobus
> technosaurus,
> Very interesting!
>
> The nobus site states that nobus is a compile-time thing, should be installed before an app such as SM is compiled.
>
> But, you are saying that the already-compiled official SM binary works with nobus?

I asked the same question and Techosaurus answered here:
http://www.murga-linux.com/puppy/viewtopic.php?p=652337#652337