From: Adam Thompson <arthompson1990@gmail.com>
To: MENGUAL Jean-Philippe <mengualjeanphi@free.fr>
Cc: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] Update Edbrowse
Date: Sat, 23 Aug 2014 14:36:11 +0100 [thread overview]
Message-ID: <20140823133611.GS2748@toaster.adamthompson.me.uk> (raw)
In-Reply-To: <53F890E9.3030401@free.fr>
[-- Attachment #1: Type: text/plain, Size: 1764 bytes --]
On Sat, Aug 23, 2014 at 03:02:33PM +0200, MENGUAL Jean-Philippe wrote:
> The package has just been uploaded to experimental repo. It will be
> available in some hours, to let the time mirror pool to see it. You can test
> it yourself, of course, from experimental.
Ok, will do.
>
> It builds properly with libmozjs24 which contains jsapi.h and what is
> needed. However, I would like to inform you that this package is not
> maintained so far, so the jsapi.h seems available rather in icedove-dev
> package (which contains headers for icedove). It means that, for any
> reasons, Edbrowse will not build properly against JS stack 31. I don't think
> it's a problem for freeze, but maybe we should consider testing this to
> prepare the future?
I'm going to have alook at this, since at the last time of checking,
the js 31 package (from experimental)
contained a broken symlink in place of jsapi.h.
Also, do you know of any docs for mozjs 31,
as all docs on the mozilla website talk about mozjs 24.
> After checking, freeze happens on November. So:
> 1. Do you want now to work on compatibility with JS 31?
> 2. Otherwise, I propose we wait end of September to be sure Edbrowse builds
> on any architecture without problem. Next, you could release in 1st 15 days
> of October. Then I could introduce the released package in sid (October,
> 15th), and it willl go to testing (and be frozen) on Octoberb 25th.
> Does it fit? Do you want a more restricted schedule?
The timings sound fine to me provided the new edbrowse package runs correctly.
Incidentally, I'd be interested to see how you built this as the last time I
tried against a Debian packaged mozjs it segfaulted as soon as you attempted to run it.
Cheers,
Adam.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2014-08-23 13:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-22 17:39 MENGUAL Jean-Philippe
2014-08-22 20:32 ` Adam Thompson
2014-08-22 20:43 ` MENGUAL Jean-Philippe
2014-08-22 22:11 ` Chris Brannon
2014-08-23 13:02 ` MENGUAL Jean-Philippe
2014-08-23 13:36 ` Adam Thompson [this message]
2014-08-23 13:47 ` MENGUAL Jean-Philippe
2014-08-30 15:11 ` Adam Thompson
2014-09-01 18:36 ` MENGUAL Jean-Philippe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140823133611.GS2748@toaster.adamthompson.me.uk \
--to=arthompson1990@gmail.com \
--cc=Edbrowse-dev@lists.the-brannons.com \
--cc=mengualjeanphi@free.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).