[ruby-talk:14997] Standard practices for module distribution

I am planning to release some Ruby modules and wonder if there are any
standard practices to follow when making the distribution, to make sure
that use of the module is as painless as possible.

mkmf.rb is great, but does not solve all my problems, for example I
need to install both binary extensions and "pure" ruby modules. Also 
there might be documentation and other things that needs to be compiled
and installed.

Is there a standard practice for doing this? If not, which is the best
way? I can think of several:

	* Override some of the functions in mkmf to add the desired
	  functionality.

	  ---> Probably not a good solution. The functions in mkmf are heavy
	  and interdependent. The distribution would probably not work with
	  new versions of mkmf.

	* Create my own version of mkmf

	  ---> Not good. If ruby is exported to a new platform, my code
	  will not compile.

	* Postprocess the Makefile after it has been created by mkmf to
	  add the desired functionality in extconf.rb.

	  ---> Probably better, but seems a bit fragile. The post_processing
	  will probably depend on superficial features in the Makefile,
	  such as names of phony targets etc. If this should change the
	  distribution would break.

	* Use several different makefiles with one Makefile to rule them all.
	  extconf.rb renames the Makefile created by mkmf and then creates
	  any additional makefiles that are needed, and finally, a Makefile
	  that runs all these makefiles.

	  ---> Seems to me like the best option.

Any thoughts?