edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Chris Brannon <chris@the-brannons.com>
To: Karl Dahlke <eklhad@comcast.net>
Cc: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] edbrowse and edbrowse-js not communicating
Date: Mon, 14 Dec 2015 20:55:26 -0800	[thread overview]
Message-ID: <87d1u8mhtt.fsf@mushroom.localdomain> (raw)
In-Reply-To: <20151114131201.eklhad@comcast.net> (Karl Dahlke's message of "Mon, 14 Dec 2015 13:12:01 -0500")

Karl Dahlke <eklhad@comcast.net> writes:

> is it possible to have edbrowse check at run time
> whether it has the correct and latest tidy, and issue a warning message if it does not?

Here's the problem.
The old tidy code defined tidyReleaseDate.
tidy-html5 defines tidyLibraryVersion and tidyReleaseDate, but they
claim that tidyReleaseDate is deprecated.  So I don't know how long that
will be available.
For now, tidy-html5 is a drop-in replacement for the original tidy, so I
suppose I could look at tidyReleaseDate to determine whether we're using
old tidy code.
A better solution would be to check at build time.
That's quite doable with cmake, and I'm starting to get a handle on how
to use it, so maybe that's the way to go.

That begs a question.  At some point, should we consider deprecating all
of our makefiles?

-- Chris

  reply	other threads:[~2015-12-15  4:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-14 15:32 Chuck Hallenbeck
2015-12-14 18:04 ` Chris Brannon
2015-12-14 18:12   ` Karl Dahlke
2015-12-15  4:55     ` Chris Brannon [this message]
2015-12-15 12:58       ` Adam Thompson
2015-12-17 10:44         ` Chris Brannon
2015-12-19 12:37           ` Adam Thompson
2015-12-19 12:58             ` 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=87d1u8mhtt.fsf@mushroom.localdomain \
    --to=chris@the-brannons.com \
    --cc=Edbrowse-dev@lists.the-brannons.com \
    --cc=eklhad@comcast.net \
    /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).