Max Vozeler wrote: > I think both points could be helped by having loop-AES and > ciphers be one software package in one tarball. It would make it > easier for users of ciphers to build and install the modules, and > last but not least would make my life as distribution package > maintainer a bit easier. :-) > > Downsides: Uncompressed tarball grows by ~90k. Users who don't > need/want ciphers still get them and, if the cipher modules were > installed by default, an additional ~45k of disk space used. > > What do you think? There are cases where people are using kernel patch version of loop-AES, and build and install those extra cipher modules without building loop-AES module. So there is some need of ciphers package staying as separate package. Would it help if loop-AES Makefile detects presence of additional loop_xxxx.c source files is its base directory, and compiles and installs them all together? Your maintenance "work" would involve making sure that all source files are in same directory. -- Jari Ruusu 1024R/3A220F51 5B 4B F9 BB D3 3F 52 E9 DB 1D EB E3 24 0E A9 DD - Linux-crypto: cryptography in and on the Linux system Archive: http://mail.nl.linux.org/linux-crypto/
