Seamonkey

Mike Hommey mh at glandium.org
Fri Sep 22 16:37:17 UTC 2006


On Fri, Sep 22, 2006 at 11:20:45AM +0200, Hendrik-Jan Heins <hjheins at gmail.com> wrote:
> Hello Mike, Jaldhar, list,
> 
> To start off with this: Jaldhar, I have been trying to reach you
> before, but without succes. And as you didn't mail in the list
> anymore, I assumed you lost interest in the work. I'm sorry, I didn't
> want to mess with stuff you are working on, but as everything seemed
> to go very quiet after your version of Seamonkey, I decided to give it
> a shot.
> For now my account on alioth is: hjheins-guest (the guest part was
> added by the system).
> 
> As for the packaging: I actually agree more with Mike on that one: I
> am a Mozilla/Seamonkey only user (so no konqueror or Firefox), but I
> don't use the complete thing. I only use the mailnews and browser
> package. So I think I'd like the idea of the separate packages and a
> install-all package for people who want the complete works.
> 
> As for the library locations: yes, I did put the libnspr and libnss
> files in /usr/lib/seamonkey as that was the only way to avoid issues
> with xulrunner packages. I also put all devel packages in
> /usr/include/seamonkey.
> At the moment I actually doubt the functionality of separate libnss
> and libnspr packages, as they serve no purpose except that they are
> needed for Seamonkey itself. So maybe they can be packaged in the
> seamonkey-browser package?

I don't think seamonkey-browser would be a good place for that, that
would make it a mandatory package if you install some other component.
A seamonkey-common or seamonkey-libs package would be more appropriate.

> As for what version to use: I don't know that much about Debian
> release cycles, but I tend to agree with Alex Vincent that it is
> useless to go for the 1.0.x version when 1.1 is so close. I actually
> have been testing with 1.1a already, and it is completely stable, so I
> see no reason to start on 1.0.x right now as 1.1 is just around the
> corner.

This has to be decided with the release managers.

> About the spellcheck libs: I just did what the old Mozilla package
> also did: I linked the myspell location of Seamonkey to the location
> of the system myspell files. This way Seamonkey uses the system
> installed dictionaries for spellcheck. In practice this means that
> /usr/lib/seamonkey/dictionaries is linked to /usr/share/myspell/dicts.
> So Mike, could you elaborate on what you mean with your remark about
> the spelling files, as I don't really understand what you want to do
> differently?

I was speaking of the libraries (libmyspell3c2 package). The firefox
package in experimental does use the system libraries instead of the
bundled myspell. That requires a minimal patch that I can provide.

Mike



More information about the pkg-mozilla-maintainers mailing list