Bruno Haible <[EMAIL PROTECTED]> writes: >> I propose to move these modules to modules/crypto/ > > Maybe it is wise to consider the dependency structure when creating this > subdirectory? The 'md4' module is not dependent on the other crypto modules, > and the other crypto modules don't depend on the 'md4' module. Why should > it then be put in the same directory? [I'm not sure, really. Just playing > the devil's advocate.]
That's true. I guess it depends on the refactor discriminator. Either based or content (crypto, unicode, string-functions, math-functions, etc), or type (header, file, etc). To me, all the crypto stuff seems self-contained and uninteresting for anyone who doesn't want to see them, and thus it makes sense to have them in a separate directory. I guess I could make a similar case for unicode functions or math functions. >> If the m4/ directory supports sub-directories, >> moving the *.m4's to m4/crypto/ would be nice too. > > I don't think it does. One would need to pass extra -I flags to 'aclocal'. > gnulib-tool doesn't do this yet. I think aclocal might as well search the entire directory tree for *.m4 rather than just -I's. There could be a --exclude if you wanted to exclude some directory. /Simon
