Seamonkey progress

[Hendrik-Jan Heins]

Ooooh I'm so going to pick your brain about this!

First of all: thanks a lot:
A lot of the changes are about the way you define how and where to
install files. I didn't dare to do it as you did it (yet), but I sort
of thought it would work like that.
I saw your "script in rulesfile" I needed that, but didn't know how to
do it, nice! I learned a lot from this!

But now on to the "real work".
I do have a lot of questions and some suggestions about your build.
First of all: Alexander, yes as far as I found out, the update script
is still needed.

Now for my points;
first about the patches
why a complete configure file? -> patch it?
-> why again setting settings here you can sat with mozconfig?
lots of "changes" are identical to the original; why?
isn't patching configure.in a better/shorter way?
why not enable embedding tests in mozconfig? (same goes for myspell
and some other stuff I saw defined in configure)
why enable them thru a patch?

what's this/what does it do: ac_add_options --with-gssapi=/usr (mozconfig)
same: ac_add_options --disable-xpcom-obsolete --disable-javaxpcom

Just a suggestion, but why not create an IceApe build directly from a
Seamonkey source package? I attached a patch with the exact thing
Alexanders source package does.
Something to remember: a symlink in /usr/bin named seamonkey -> iceape
is probably needed for compatability reasons. Gaim for instance will
include a seamonkey connection in 2.0beta4.

what about my jar compress patch? Are you already using that? (your
jars are compressed mine weren't by default)
What about my patch for the browsertype and help pages (I placed that
on the list a couple of e-mails ago, I think it is needed when you
make it into IceApe; there you can also define the default project
page)

why the /etc/pref/<thingie> instead of /etc/prefs.js ?
why install .autoreg?  it's generated anyway.
I think all "dom_*" files in base should (and can) be in the
dom-inspector package.


Now about the workings of the packages:

with only base and mailnews installed: cannot compose mails; read html
mails etc...
your current version won't work in anything but basemode with gmail

hmm, is it somewhat unstable (not sure!)?
-> killed itself with this error:
symbol lookup error: /usr/lib/seamonkey/components/libctl.so:
undefined symbol: pangolite_find_map

do I understand from your seamonkey-runner file that you by default
disable pango?
-> export MOZ_DISABLE_PANGO

Hendrik-Jan

2006/10/12, Mike Hommey <mh at glandium.org>:
> Hi all,
>
> I uploaded test packages on
> http://people.debian.org/~glandium/seamonkey/
>
> I haven't extensively tested the programs yet, but everything should be
> fine.
>
> The changelog is not very up to date, especially the date, but
> basically, I made so much changes that it's almost as if I started from
> scratch.
>
> The upgrade path is not handled by the maintainer scripts yet, I was
> actually wondering if I'd rather do it in seamonkey or in the mozilla
> transition package (which, as you may see in the conflicts I'm planning
> to version 2:1.8, speaking of which, if we make transitionning in the
> mozilla package, we don't need conflicts at all).
>
> Hendrik-Jan, if you want to discuss the whys and the hows of some of the
> changes, please ask, I'll try to make my answers crystal clear for a
> change ;)
>
> There may still be some glitches, because hurrying doesn't help much
> with perfection, though knowing that the freeze would be delayed made
> me relax a bit...
>
> Note that I didn't include the debian specific start pages for the mailer
> and the browser because, since we are going to change from seamonkey to
> icedove, I was thinking we would have to change the original ones
> anyway...
>
> Anyways, I'll start s/seamonkey/icedove/ in the debian directory asap,
> so that all that will remain will be the source tarball. Let's just
> hope everything works correctly with my packages, and let me know what
> you think is best for the transition from mozilla, I'll adapt the
> debian directory to fit the final choice.
>
> Cheers
>
> Mike
>
> _______________________________________________
> pkg-mozilla-maintainers mailing list
> pkg-mozilla-maintainers at lists.alioth.debian.org
> http://lists.alioth.debian.org/mailman/listinfo/pkg-mozilla-maintainers
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: app_name.dpatch
Type: application/octet-stream
Size: 572 bytes
Desc: not available
Url : http://lists.alioth.debian.org/pipermail/pkg-mozilla-maintainers/attachments/20061012/4d5c04f1/app_name.obj