[m-dev.] bytecode stuff in cvs repository

[Bert Thompson]

Quick summary:
	- The code should not be in the source release.
	- I want it checked in for regression tests.
	- Formal source release should not include the whole
	  kaboodle. We should have a script for bundling source dist.
	- I'm willing to do it.

|Hi Bert,
|
|I notice that you checked in a bunch of code into a directory
|`mercury/bytecode' in the CVS repository.  This has unfortunate
|consequences, e.g. that code will get automatically included in
|the source code distribution tar.gz file.  Since this code has
|not been reviewed, that is a bug.  Can you please fix it
|(somehow, e.g. by removing those files from the CVS respository --
|I'm not exactly sure how to do that without causing problems, so be
|careful.)

Andrew reviewed the code.

You're right. It shouldn't be in a source release since it's very
much work in progress. However I want the source checked in since 
I want to have regression tests running on it. This is inconvenient 
if it's not checked in. 

|And can everybody else please take note that the `mercury' subdirectory
|of the CVS repository is reserved for things that will actually be
|included in the Mercury source distribution?  Anything checked in
|there may be released to the world tomorrow.

If everything automatically gets bundled into the source distribution,
then I would consider this to be a bug. I'm willing to fix up
the release process if no-one else is inclined to.

A simple fix is to have a list of directories that get bundled and 
little shell script to do the bundling should be enough.[*]

Bert

[*] Standard practice is to have a formal release process one of whose 
steps is to bundle up the stuff in the `bill of materials'. There are
some Usenix conferences on this sort of development practice. I've
also seen some HP internal docs outlining similar processes.