> From: Rodent of Unusual Size [mailto:[EMAIL PROTECTED] > Sent: Monday, December 11, 2000 11:57 AM > > Greg Stein wrote: > > > > Okay... we seem to have some general agreement to make a "non-core" > > APR package that contains the "purely portable" items. With that in > > mind, here are my rough ideas/notes on this: > > I missed this discussion, and so I guess I'm stuck with something > I find truly gross and disgusting. IMHO, there should be ONE > CVS module for APR, and specific areas can be segregated below > that. If some wants to deal with only part of it, like the > iconv stuff, they can very easily check out just that subdirectory. > Having separate modules beyond "apr" and "apr-site" is completely > bogus -- again IMHO. Euw.
Problem - if the module is 'nested', it becomes very hard to 'exclude' just a portion, such as iconv. Likewise, apr-util may become rather large in and of itself. If an author is interested -only- in portability, they check out apr. If they want our idea of great stuff, they also grab apr-util. If they need a portable iconv, they grab apr-iconv. If they don't care, they can ignore the issues. The only -other- option would have been (in 20/20 hindsight that none of us is blessed with) an empty top level apr, with core, util, iconv, and any one of a number of sub-libraries, of which any set could be layered on core. Since that isn't the module's structure, this is what we've got.
