Bruno Haible <[EMAIL PROTECTED]> writes:
> Objections?
Refactoring seems like a good thing. Your proposed two modules/
directory split didn't strike me as the obvious way to go, but I
haven't really thought about it.
Btw, a lot of modules would go away of I moved all crypto-related
stuff into a separate directory. There is:
[EMAIL PROTECTED]:~/src/gnulib$ ls modules/gc*
modules/gc modules/gc-md2-tests
modules/gc-arcfour modules/gc-md4
modules/gc-arcfour-tests modules/gc-md4-tests
modules/gc-arctwo modules/gc-md5
modules/gc-arctwo-tests modules/gc-md5-tests
modules/gcd modules/gc-pbkdf2-sha1
modules/gc-des modules/gc-pbkdf2-sha1-tests
modules/gc-des-tests modules/gc-random
modules/gc-hmac-md5 modules/gc-rijndael
modules/gc-hmac-md5-tests modules/gc-rijndael-tests
modules/gc-hmac-sha1 modules/gc-sha1
modules/gc-hmac-sha1-tests modules/gc-sha1-tests
modules/gc-md2 modules/gc-tests
[EMAIL PROTECTED]:~/src/gnulib$
And plus modules for each of the underlying modules (e.g., arcfour,
arctwo, des, md2, md5, ...) plus their test modules.
I propose to move these modules to modules/crypto/ and all the *.{c,h}
files to lib/crypto/. If the m4/ directory supports sub-directories,
moving the *.m4's to m4/crypto/ would be nice too.
None of these modules are intended to replace any standardized API.
I'm Cc'ing Jim because he is the owner of the md5 module. I believe
md5 is the only crypto-related module that I'm not the owner of. Jim,
are you ok with moving the md5 module to modules/crypto/ together with
the rest of the modules?
/Simon
