Seamonkey and Seamonkey libs update for Slackware 13.1?
SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
The latest version of Seamonkey requires a newer version of Cairo than what's installed.
checking for cairo >= 1.10 pixman-1 freetype2 fontconfig... Requested 'cairo >= 1.10' but version of cairo is 1.8.8
configure: error: Library requirements (cairo >= 1.10 pixman-1 freetype2 fontconfig) not met;
At this point, I'll probably upgrade cairo and pixman and then try the upgrade to Seamonkey. If all of that monkey's up my system (pun!) then I'll install Slackware 13.37 (actually do the upgrade) and be done with it.
Upgrading Cairo is actually something of a big deal. Seamonkey 2.2 didn't build; it stopped part way through with an error about a missing directory (I think in the build tree).
I didn't have time to track down the error in more details tonight, but it doesn't matter. The new version of Cairo seemed to be responsible for severe instability in my installed versions of Firefox and Thunderbird. I think I would have to rebuild them with the new Cairo too -- and that's just not worth the trouble.
I haven't tried just installing the version from 13.37 to see if it works, but if Cairo is a build-dependency, it may also be a runtime dependency.
So, we seem to be in the unfortunate circumstance that major software updates to Seamonkey are only supported for the latest version of Slackware.
Why does Slackware still have SeaMonkey anyway? I know it's the core/foundation project for all the Mozilla stuff, but do we actually really need it? Can't you just use XULRunner and SeaMonkey-SoLibs in place of the full SeaMonkey package, or is SeaMonkey really that required?
Slackware started including the Seamonkey suite when de Mozilla suite was discontinued (back in the day when Firefox and Thunderbird were launched).
Except maybe for Konqueror in KDE, no browser is really required. I think it is nice that we have Firefox and links and lynx and Seamonkey in addition to konqueror. I use all of them (except links).
The advantage of Seamonkey is that it is a suite, not just a browser. It also includes a mail client and maybe even more.
The advantage of Firefox is that it has a large market share, so many websites are built to work with FF.
The advantage of lynx is that it doesn't require X.
The advantage of konqueror is that it starts up faster if you're already using KDE.
They all have their uses. They may not be required, but each one is different enough from the next. IMO, Seamonkey isn't just another browser.
BTW, the solibs are a separate package on slackware, so you can have just the solibs if you want.