Ah, yes - I see now. I'm ok with extras/qmf/qmf[2], but that begs the
question - what about non-python QMF stuff, like other language bindings and
cross-implementation interopt tests?
If we end up moving all qmf-related stuff into extras, then we'd probably need
flesh out a bit more structure for that qmf subdir. e.g.:
extras/qmf/python/{qmf, qmf2, tests, ...}
extras/qmf/cpp/{...}
extras/qmf/bindings/{....}
extras/qmf/tests/{...}
Thoughts?
-K
----- "Rafael Schloming" <[email protected]> wrote:
> Ken Giusti wrote:
> > Hi,
> >
> > I've no problem with a cleanup reorg, but I'd like to keep the qmf
> version in the dirname (wherever it may end up). e.g.:
> >
> >>> qmf/ ---> qpid/extras/qmf/
> >>> qmf2/ ---> qpid/extras/qmf2/
>
> Ah, I was a bit unclear in my notation, I was thinking of
> qpid/extras/qmf/qmf, and qpid/extras/qmf/qmf2, assuming that they
> would
> share license, install, and packaging bits, but I'd be happy to do it
> as
> above as well if you wanted qmf and qmf2 to be separate directories
> within extras.
>
> --Rafael
>
>
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project: http://qpid.apache.org
> Use/Interact: mailto:[email protected]
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
