Return-Path: Mailing-List: contact dev-help@apr.apache.org; run by ezmlm Delivered-To: mailing list dev@apr.apache.org Received: (qmail 62191 invoked from network); 16 Dec 2000 14:57:26 -0000 Received: from 3ff8faf3.dsl.flashcom.net (HELO koj.covalent.net) (63.248.250.243) by locus.apache.org with SMTP; 16 Dec 2000 14:57:26 -0000 Received: from rbb (helo=localhost) by koj.covalent.net with local-esmtp (Exim 3.16 #1) id 147IoR-0001KT-00; Sat, 16 Dec 2000 06:59:51 -0800 Date: Sat, 16 Dec 2000 06:59:51 -0800 (PST) From: rbb@covalent.net X-Sender: rbb@koj.rkbloom.net To: Greg Stein cc: dev@apr.apache.org Subject: Re: src/ directory (was: Re: Showstoppers: Alpha 9) In-Reply-To: <20001214031030.X8951@lyra.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N > > I think it is goofy to place a src directory in a source tree -- everything > > in the distribution is source. If there are too many subdirectories, then > > either abstract them into relevant categories or split them into different > > library modules. > > It isn't "a source tree". There is a lot more in the CVS repository than > just source. There are build mechanisms, documentation, test programs and > framework, public include areas, etc. > > Categorization is quite difficult: consider APR's 15 source subdirs. How > could those possibly be grouped? It is very easy to group parts of APR. This is just off the top of my head, and without looking at all the dirs, IO/ file_io network_io mem/ shm pools (currently called lib) I'm sure that looking closer will provide many more examples. Ryan _______________________________________________________________________________ Ryan Bloom rbb@apache.org 406 29th St. San Francisco, CA 94131 -------------------------------------------------------------------------------