Bug#350740: new version

To: 350740@bugs.debian.org
Subject: Bug#350740: new version
From: "Hendrik-Jan Heins" <hjheins@gmail.com>
Date: Sun, 10 Sep 2006 21:01:34 +0200
Message-id: <[🔎] 871179400609101201q3e90e60fhb29d86cfc2434d24@mail.gmail.com>
Reply-to: "Hendrik-Jan Heins" <hjheins@gmail.com>, 350740@bugs.debian.org
In-reply-to: <871179400609100151j6c8e2410y68bfe0b63c6dd642@mail.gmail.com>
References: <[🔎] 871179400609080723t52cdea5fied1b2e361ec8f32f@mail.gmail.com> <[🔎] 9301ed6b0609080925u12aa892brd0f13cd29056558a@mail.gmail.com> <871179400609081036w7229e095qf36a7c943a8d4bad@mail.gmail.com> <9301ed6b0609081046n7bedafbeq5f1801a36c50ab1d@mail.gmail.com> <871179400609081143h717c4049t3435dbecb100266a@mail.gmail.com> <871179400609100151j6c8e2410y68bfe0b63c6dd642@mail.gmail.com>

Hello list

I just chatted a bit on the #seamonky channel on irc.mozilla.org as
Alex suggested.
Unfortunatly "oficially" no xulrunner solution for seamonkey exists yet.

What I did, is build a version that runs on xulrunner libs.
This has some unfortunate side-effects: Seamonkey isn't 100% stable on
these libs.
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.

Hendrik-Jan

Reply to:

References:
- Bug#350740: new version
  - From: "Hendrik-Jan Heins" <hjheins@gmail.com>
- Bug#350740: new version
  - From: "Alex Vincent" <ajvincent@gmail.com>

Prev by Date: Bug#386865: O: pipsecd -- IPsec tunnel implementation
Next by Date: Bug#386878: ITP: ink -- tool for checking the ink level of your local printer
Previous by thread: Bug#350740: new version
Next by thread: Processed: title
Index(es):
- Date
- Thread