search

bitwiseworks / mozilla-os2

Mozilla for OS/2 and OS/2-based systems
Other
33 stars 9 forks source link

Build Seamonkey #11

Open AndiB-2 opened 11 years ago

AndiB-2 commented 11 years ago

Support ticket for Seamonkey with included email client chatzilla and calendar.

People used to Seamonkey dialogs are usually not happy with Firefox look and feel. Anyone who want to have Seamonkey ported to eCS too should add a note here.

stephanbucher commented 11 years ago

I have been using Seamonkey for years (and Mozilla and Netscape Navigator before), and I would welcome if support for the OS/2 platform continued.

dryeo commented 11 years ago

Once Thunderbird is building, it should trivially take a few kmk files to build SeaMonkey. It'll be like the 2.7.2 releases, unofficial as SeaMonkey does not support ESR builds.

cultor1 commented 11 years ago

I want to have Seamonkey ported to eCS too.

fbakan commented 11 years ago

I also like SeaMonkey more than Firefox...

abwillis commented 11 years ago

Dave, I hope you are right, I have no use for Firefox. While I have built things for years with kbuild I have never understood it nearly as well as I did the Mozilla build system, though with the new python build environment that is not necessarily the case any longer.

losepete commented 11 years ago

I also prefer Seamonkey to Firefox

dryeo commented 11 years ago

Hi Andy, I don't know much about kbuild either though the way Dimitri describes things it should be easy and nothing much has changed in the Mozilla build system since 10esr. 24esr will be harder to do the configure route without some python stuff ported (eg virtualenv, https://pypi.python.org/pypi/virtualenv) or worked around.

losepete commented 11 years ago

Looks like I've been automatically CC'd.

Now to try and discover how to get un-CC'd at githuib which is not the most intuitive website I've ever visited.

dryeo wrote:

Hi Andy, I don't know much about kbuild either though the way Dimitri describes things it should be easy and nothing much has changed in the Mozilla build system since 10esr. 24esr will be harder to do the configure route without some python stuff ported (eg virtualenv, https://pypi.python.org/pypi/virtualenv) or worked around.

Reply to this email directly or view it on GitHub: https://github.com/bitwiseworks/mozilla-os2/issues/11#issuecomment-18718738

effectuator commented 11 years ago

Another vote in favour of Seamonkey!

dmik commented 11 years ago

@losepete, it's an issue tracker, not a poll manager. If you comment on the issue, it is expected that you are interested in observing its progress. If you are not, the Unwatch thread button at the bottom of the page should help you. Quite easy.

thomabrown commented 11 years ago

I have no use for FF either. I have used SM as long as I can remember. I just wish it were a bit more stable. It either freezes or vanishes with or without an entry in popuplog.os2. 38 *.trp files since 2012-06-17. Almost all of mey problems occur while reading CNN. Perhaps I should look into reporting some of these...

SilvanScherrer commented 11 years ago

Please don't add new "I want Seamonkey as well" comments. We know now that the demand is there.

dryeo commented 10 years ago

It would be nice to also have betas of SeaMonkey and Thunderbird. This would result in more testing as Firefox is still very slow. With luck there should be only minimal patching involved to build. Also betas should be nightlies without setting --enable-official-branding.

dmik commented 10 years ago

Well, I don't agree that they should be nightlies. Firsrt, nightlies are nightlies, not betas. Even the official Mozilla policy is to release betas with normal Firefox branding. Second, our OS/2 betas are not the same as Mozilla betas. We are based on Mozilla GA releases, and "beta" (and soon "RC" and "GA") only relates to the status of the OS/2 port itself.

LewisR commented 10 years ago

Just another vote for SM. I also maintain a number of modified FF & TB extensions which install and run under SM. I do most of my development on eCS, so as a result, things like my tweaks for FireFTP are lagging well behind the official releases for FF (luckily, Mime incorporated most of my changes into the official repo, though my work on the statusbar icon is as yet unofficial).

I'll leave it to the project team to determine the build/release frequency. For me, I don;t mind testing on FF, but I prefer a stable SM build for my daily work, as it's kind of hard to get things done when things like email are misbehaving. ;-)