Response to Mike's readme

Hendrik-Jan Heins hjheins at gmail.com
Sat Sep 23 12:43:29 UTC 2006


Hello All,

In this e-mail I want to address Mike's issues as he proposed in:
http://people.debian.org/~glandium/seamonkey-patches/README

First off: I based the current versions of the package on the old
mozilla-suite. So the current builds are probably not the way things
should be packaged.
Next: I am not a programmer! I only used to package .RPM files for
several distro's before, so there's also a lot of Debian specific
stuff that I do not know about. Feel free to correct me.

Ordering and naming: Sorry, don't know anything about it, so nothing
from me here,
Patches:
Icons is an issue: the builds I currently did contain and use the
standard Mozilla icons, with the addition of the Seamonkey icon. A set
of other/new icons might be a good idea,
A lot of the other patches I can not comment on, as I have no idea
what the difference is between the default behavior and what the
patches do.

As for the profile: Seamonkey uses profiles. If it does this based on
the default profile, we need to keep it. I'll have to do some tests to
know how this works.

The useragent patch: In the current builds, it is already seen as
Seamonkey Debian build, so not sure if this is needed.

I don't particulary like cdbs either, but I know too little about the
inner workings to know how to build this in any other way.

On the mozconfig patch we agree. But up till now other methods killed
the build with a config error. Let's see if it works better with the
method you suggested. I already made a mozconfig file, so we were
thinking along the same lines.

The --enable-ctl parameter: Don't know. I'll do a testbuild without it.

MOZ_ENABLE_COREXFONTS is not used in the current builds.

MOZ_OBJDIR: as far as I understand it, this is just an alternative
build dir. We can also do the build in de package source itself, that
should not really make a difference.

I am NOT opposed to a -dev package. I don't want to say that it will
be needed very often, but it is easy to package, and you don't have to
install it if you don't need it.
It does not interfere with the xulrunner dev packages so, I'd just
package it anyways.

Yes, Mozilla needs to provide the transition packages. The sooner we
can get rid of those epoch settings, the better.

In the current builds, the standard Seamonkey dir is
/usr/lib/seamonkey (so no version number). I think that is the best
location for it. No need to use version numbers.

"-O2 -g -fno-strict-aliasing" are used together. For ppc64
"-mminimal-toc" is used.

The comment about FIPS:  eeeh, you lost me there, sorry!

I think a sort of "seamonkey-common" package is possible. I'm not sure
how much of the browser can be left out of it, as the mailer also uses
the html engine for rendering (html)mail. A seamonkey-browser package
with stuff like boorkmarks, and browsercore is possible, but I don't
know how much else I can leave out.
Maybe we should just make the Seamonkey-browser package the one that
also contains the common files. It is the easy way out...

So far my thoughts.
Any comments, pointers?

Hendrik-Jan



More information about the pkg-mozilla-maintainers mailing list