directory structure

[David Relson]

At 05:58 PM 2/2/03, Matthias Andree wrote:

>On Sun, 02 Feb 2003, David Relson wrote:
>
> > I have a working bogofilter configuration with a src directory (which
> > includes dcdflib).  The tests directory is still at the top
>
>Does it include "make distcheck" support? That's the common problem.

"make check" works fine.  "make distcheck" successfully builds all programs 
and all the regression tests (except bogoutil/driver.sh) work fine.  The 
problem with driver.sh is an incorrect path which I haven't solved yet.

> > level.  src/Makefile.am doesn't allow ../tests in SUBDIRS, which seems to
> > mean that "make check" must be run from the top directory or else tests
> > should be a subdirectory of src.
> >
> > What are your thoughts on best organization for src and tests?
>
>If we want to save our time for real work, we'll leave it as it is now.
>Getting the history transferred without direct repository access isn't
>possible AFAIK, and moving /everything/ to src isn't really useful. Or
>am I missing something?

At the moment, there are too many files in bogofilter's main 
directory.  The count is just under 200 files, including generated .o files 
and executables.  My goal is to move source code to src.  That appears to 
be approx 180 files.  This will improve the overall file organization and I 
think will be useful in the long term.  When I queried the list on this 
subject a month ago, there were more votes for the re-org than against it.

It would be nice if we had access to the cvs repository at SourceForge and 
could move files around, but they don't permit that.  I'm willing to start 
afresh without file history for the sake of the cleaner organization.  If 
desired, we could record the current history and include that info in doc.