What packaging rules for an arch-independent GEdit plugin?

[Ben Finney]

Ben Finney <bignose at debian.org> writes:

> The build dependencies are all architecture-independent, and as far as
> I can tell the build and installation process is
> architecture-independent.
>
> The upstream install script consists essentially of copying some files
> to ‘/usr/lib/gedit/plugins/’.

An example of this is the GEdit plugin from the ‘rabbitvcs’ source
package. Apparently it relies on ‘dh_install’, to simply install the
plugin files directly to ‘/usr/lib/gedit/plugins’.

How should a third-party GEdit plugin, architecture-independent Python
code, be packaged for Debian so that it will work correctly in GEdit?

-- 
 \          “I got an answering machine for my phone. Now when someone |
  `\      calls me up and I'm not home, they get a recording of a busy |
_o__)                                          signal.” —Steven Wright |
Ben Finney