Change Password Utility (CPU) gives system administrators the ability to administer users and groups on a wide range of backends, currently including LDAP and flat files. Simply, CPU is for user and group administration. The commandline is almost completely compatible with existing Linux user and group management tools, so it can easily be dropped in place. It supports several different hashing algorithms and allows existing users to be imported from Unix-style passwd and shadow files into the backend of your choice.
As a project admin, I run into these problems. But that's only because I am having to generate all the configure files. As a user, you should never run into these issues using the Autotools, since the files you get have all been generated before hand. There is no need for m4, autoconf, automake, or any of the other autotools if you are an end user. The only tools you should need as an end user for compilation, are the bourne shell and a version of make. If you are a developer using the autotools, accept the fact that all the developers need to roughly be using the same version of the Autotools. Making this concession is a pretty reasonable tradeoff considering the ease it brings to your users in compilation, and the ease it brings to developers in terms of both increasing portability (autoconf does system checks I wouldn't otherwise think of) as well as decreasing the ammount of time needed for a development cycle.
> Has anyone else never had a single
> problem that Andrew points out? Or does
> anyone else not see any of what he
> points out as a problem? I've been
> building from source for a helluva long
> time and I have yet to find a auto*
> problem that didn't have a simple fix.
> Is anyone else NOT have problems?