> Definitively the single-file ones, not entierly sure for the > multi-file ones.
I have no particular feeling about single-file utilities, but I'd be definitively against dropping all multi-file ones in a single directory. That would create a mess. Just dropping the files into a single directory would indeed be a mess. That wasn't my plan, I'll try to play around with it and see what becomes of it. I can start putting the single-file ones in src/ though if everyone is OK with that. And then send a patch for review for the multi-file ones. Notice also that there is a difference between core- and inetutils: our configure.ac gives installer a possibility to build only a subset of all utilities. So does coreutils using --enable-intall-program/--disable-install-program. The current implementation of this is suboptimal, as it was written back ago when Automake did not support DIST_SUBDIRS. The latter would greatly simplify it, but it relies on each utility residing in its dedicated subdirectory. I don't think that using DIST_SUBDIRS would be much cleaner vs. using bin_PROGRAMS = @ftp@ ...; which is what we currently do (more or less).
