The problem is that I've already invested heavily in Foo.pm. So, in order to do this, I'd have to copy the module over, delete the already existing code, and change the name of the module not only in the package statement, but the POD as well. Repeat for the testing. It just seems rather silly that h2xs (and Module::Starter from what I've seen of it) assume that you'll know every class that will go into a distribution at the time of creation. CWould it be a bad idea to rework these tools so that instead of failing to create a file, it would test for existance first and if it exists say something like "Foo.pm skipped: already exists"? If it's not a bad idea, then I could even do the work. Ah...to see my name somewhere "official"...