edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] 3.6.0
Date: Mon, 26 Oct 2015 12:42:49 -0400	[thread overview]
Message-ID: <20150926124249.eklhad@comcast.net> (raw)

As the windows port marches on to success, we may want to pause,
and finish everything currently in progress, and test, and debug,
and then call it 3.6.0.
This brings in some questions,
which I am in no way qualified to answer.

linux:
We want to keep this easy and clean for our distributers, debian, ubuntu, bsd, etc.
Will they git and package a version of tidy5, specifically 5.1.15,
as prerequisite to packaging edbrowse?
In other words, a package dependency?
Or will edbrowse build and distribute with tidy linked in as a static library,
so there are no additional package dependencies?

windows:
Same question about tidy, but also questions about mozjs.
Given the additional complexity of mozjs in windows, should we package
edbrowse and edbrowse-js separately, the latter depending on the former?
Or is it just as easy to bring them both in together.
How can casual windows users, who may not be experts in windows
installation processes, download and install edbrowse?

Chris will maintain his static binaries on edbrowse.org,
are there meaningful .exe files he can build and maintain for windows users?

Are there other bugs we need to fix, small enhancements we need to make?
In particular, (Kevin), are we miles away from jQuery,
wherein that should wait for 3.6.1, or would a few more small changes get us there?

Couple open issues with tidy but I'm working around them
so maybe they too should wait.

We should all browse around various sites on the net,
looking for seg faults, or mangled pages,
or other various bugs.
I imagine most of us do that in the course of our daily work and play.

Looking forward to 3.6.0.

Karl Dahlke

             reply	other threads:[~2015-10-26 16:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-26 16:42 Karl Dahlke [this message]
2015-10-27  6:30 ` Kevin Carhart
2015-10-27 21:00   ` Adam Thompson
2015-10-28  6:59     ` Kevin Carhart
2015-10-27  9:03 ` Chris Brannon

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=20150926124249.eklhad@comcast.net \
    --to=eklhad@comcast.net \
    --cc=Edbrowse-dev@lists.the-brannons.com \
    /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).