[qmtest] [b,s]dist creation

[Mark Mitchell]

> I'd be fine with both. Actually, I'm aware that the current MANIFEST
> template is too inclusive. That's partly because I don't fully understand
> the current directory structure and partly because I hope that once this
> build system is fully working we could clean the layout up a bit, i.e.
> make the source tree more isomorphic to an installed tree. Then the
> MANIFEST.in would be straight forward and clean.

We could also go to the other extreme, via something like:

  cvs export -d tmp 
  (cd tmp; find . -type f) > MANIFEST.in

Having to manually update MANIFEST.in seems bad, and using wildcards
seems dangerous, and the thing I suggest here seems cumbersome.

> For a temporary solution it would probably be most efficient if you fixed
> that file as you know best which files are official and which are not.

I think the file is OK, it is just that it is only safe to use it in a
completely virgin checkout.

> yeah, I now remember that from RH 8, and found a solution at
> http://www.rpm.org/hintskinks/rpmbuild/
> 
> I'v been running RH 9.0 for a while, and there it works again.
> 
> Of course, if this turns out to be a problem I have to extend the 'bdist_rpm'
> command to use 'rpmbuild' instead.

I think we should do that.  RH 8 is going to be around for a while, and
"rpmbuild" will work on all future systems, presumably, so by doing a
little extra work we make things more reliable for our users.
 
> Well, I would suggest to rename/move the 'qmtest.py' file then (and others),
> so yes, the man pages need to be adjusted accordingly. Speaking of the
> windows executable: I'd very much like to make it (at least optionally)
> install two scripts: one that can be run from the windows cmd, the other
> from a cygwin shell. I believe the latter could be a tiny wrapper shell
> script, so not a big deal.

That makes sense.

> Can I check it in then with these changes applied or do you prefer another
> patch first ?

It's OK to check it in.  Normally, we try hard to avoid having
unfinished work in CVS, but we've already started down this road with
distutils, so I think it makes sense to keep going in that way.

Thanks,

-- 
Mark Mitchell
CodeSourcery, LLC
mark at codesourcery.com