#!html
<pre>
t.plugin writes the dropin.cache to the package's directory. However, it's not
uncommon for that directory to be read only, i.e. when Twisted is installed to
site-packages but all the Twisted apps run as a non-root user. Perhaps t.plugin
should cache in memory instead or as well writing to the package dir?
</pre>

#!html
<pre>
It is intended that the install process write the cache files.
</pre>

#!html
<pre>
Would someone explain how this works?
</pre>

#!html
<pre>
Searching for any type of plugin in a package is enough to write the
dropin.cache to the package directory. It should be enough to load up Twisted's
IServiceMaker plugins once Twisted has been installed.

I'm not sure of the correct way to load IServiceMaker plugins but
twisted.scripts.mktap.loadPlugins() looks like a reasonable choice. However:

  * Are there any other Twisted plugin types that need loading at
    installation time that moonfallen and radix should know about?
  * What about other packages/applications that provide/use plugins? Should
    they be catered for better?
</pre>

#!html
<pre>
Committed r13679.
</pre>

#!html
<pre>
Yay Windows.

Anyone feel like getting the other installers (bare setup.py, .dpkg, .rpm?) to
do this, too?
</pre>

#!html
<pre>
Cross referencing to issue 1126 "Packge Twisted using Eggs/EasyInstall" because
they probably affect each other.
</pre>