Bug#351430: seamonkey for etch ?

Mike Hommey mh at glandium.org
Fri Sep 22 05:27:40 UTC 2006


On Thu, Sep 21, 2006 at 10:24:16PM -0400, Jaldhar H. Vyas <jaldhar at debian.org> wrote:
> On Fri, 22 Sep 2006, James Westby wrote:
> 
> >Hi all,
> >
> >Sorry to but in, but have you seen the log of
> >
> >http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=350740
> >
> >This guy seems pretty interested and active. It seems your work and his
> >are uncoordinated at the moment though.
> >
> 
> I agree.  Hendrik-Jan  if you have an account on alioth.debian.org can you 
> tell me the name.  Or if you don't have an account, can you set one up? 
> Then I will arange for you to get access to the seamonkey SVN repository.
> 
> 1.1 sounds like it should go to experimental.  For etch we should 
> concentrate on 1.0.5 or whatever is the most recent stable version IMO.

I think we should try to talk with the release managers. All new major
versions of mozilla products are going to be released just after the
hypothetical date of the freeze, but since upstream will drop support
for the current branches within six months after etch hypothetical release
date, that means we'll be on our own for security support quite quickly.
On the other hand, the soon to be released branches will be supported at
least 6 more months, which means we'll be on our own much later. It is a
better long term support plan...

> I've already mentioned this to Alexander but I'll say it again, IMO 
> seamonkey should be one package rather than split up.  It is supposed to 
> be an Internet suite after all and people who want a more fine-grained set 
> of packages can use firefox et al.

I think we should not impose to users who currently use mozilla-browser
and al. packages to have everything installed. A meta seamonkey package
installing all the fine grained packages would be a good thing though.
I know quite a lot of people, including me in the past, using mozilla-browser
only, and not caring about the composer or the mail client. Some other
do only use the composer and might want to install only it (though these
ones would be better using nvu, but composer is going to be somehow
resurrected)

> btw, I might get some time to work on seamonkey again soon.  I have 
> already uploaded 1.0.5 for Linspire but their standards and ours are 
> different so I can't simply copy my existing package.

I still insists on all the things I said before my vacation, about the
patches and all. Please do consider all that, and/or comment
http://people.debian.org/~glandium/seamonkey-patches/README

Now, some comments on Hendrik-Jan messages:
> Unfortunately, building Seamonkey on its  own libs (and shipping
> them), is also a no-go as the libnspr4-dev and libnss3-dev packages of
> xulrunner then conflict with it.
>
> If anyone knows of a way around this, feel free to comment on this.

Don't ship the libraries in /usr/lib. Ship them in /usr/lib/seamonkey
like firefox does. You can put them in a common package on which all the
seamonkey packages will depend, if you will.

> The system myspell dictionaries are now correctly linked (were in
> components, are now in dictionaries).

Please consider using the system myspell libraries. I have a patch for
that, that is already applied to firefox 2.0b2 in experimental.

> - transition/dummy package (how do I do this?)

The only solution is to make these transition packages from the mozilla
source package, because they have an epoch.

Cheers

Mike



More information about the pkg-mozilla-maintainers mailing list