Don't you see what you both report here are a same problem
with the Python code, not the C code? :)
My guess it that both
eNti and the
Arch Linux user are having problems with the automated
rewrite of the adesklets Python package that automatically
occurs whenever
src/adesklets.c or
src/command.c is refreshed (see
scripting/prototypes.sh).
After you applied the patch on a clean adesklets-0.4.12
source tree (the extraction by
cs-cam seems correct), you can bypass the
rewrite by doing:
touch scripting/prototypes scripting/enums
P.-S. All these complex sandboxes (portage, pacman, ...) are
not necessary for accurante bookkeeping of most
autotools-based packages. Try this as a non-superuser in
place of
make install:
make DESTDIR=$HOME/fake_root install
This works 95% of the time (it does with adesklets). And if
it doesn't, well, no harm is done. Going through a complete
repackaging/instrumenting/installing cycle everytime you want
to test a little something would really be a pain.
P.P.-S. I am confident the proposed modification is not
faulty. I ever you go nowhere with this, just wait for
adesklets 0.4.13 or 0.5.0 to come out pre-packaged in a
couple of weeks.