On Tue, Mar 25, 2003 at 04:36:52PM -0500, Ed Warnicke wrote:
> I'd rather that
> A) Collapse configure and epan/configure into one (and maybe
> wiretap/configure)
> not occur for the following reason:
> I'd like to see epan and wiretap independently distributable at some
> point so that they can be used by applications other than
> ethereal and tethereal. I suspect there are others here who share
> similar ambitions. Collapsing epan/configure and wiretap/configure
> into configure moves us further from this goal.
While I expected that argument for wiretap :) I don't really see this
happening with epan: I think the api would change too often - but maybe
I'm wrong. Actually A) should be done after B), if at all: It makes the
properties of a libepan (or whatever name) much clearer.
Ciao
J�rg
--
Joerg Mayer <[EMAIL PROTECTED]>
We are stuck with technology when what we really want ist just stuff that
works. Some say that should read Microsoft instead of technology.
