Hello.
I'm gonna take this thread to inform you what I'm currently doing so we can keep in touch.
You may add me in jabber if you have it. If not there's a link in my sig how you can set it up for another IM protocol like ICQ, so you won't have to get it for these purpose only.
However, the current was to set the shortcuts binding is rather rude and set it to command_1 no matter if this is set already. I wrote a little while loop to check for unset commands and take the first unset slot to set the binding.
*edit*
Corrected both, postin and postun
Proper postint and postun scripts should look like
Code:
#!/bin/bash
## pre installation
i=1
_A="/apps/metacity/keybinding_commands/command_$i"
while [[ "`gconftool-2 -g $_A`" != "" ]] ; do
i=`expr $i + 1`
_A="/apps/metacity/keybinding_commands/command_$i"
done
echo "`basename $_A` is unset yet, will set it to \"gloobus-preview\""
# doit
#gconftool-2 -s --type string $_A "gloobus-preview"
_B="/apps/metacity/global-keybindings/run_`basename $_A`"
echo "keybindings for $_B set to \"<Control>space\""
# doit
#gconftool-2 -s --type string $_B "<Control>space"
and
Code:
#!/bin/bash
## post uninstallation
i=1
_A="/apps/metacity/keybinding_commands/command_$i"
while [[ "`gconftool-2 -g $_A`" != "gloobus-preview" ]] ; do
i=`expr $i + 1`
_A="/apps/metacity/keybinding_commands/command_$i"
done
echo "Unsetting $_A "
# doit
#gconftool-2 -s --type string $_A ""
_B="/apps/metacity/global-keybindings/run_`basename $_A`"
echo "Unsetting keybindings for $_A"
# doit
#gconftool-2 -s --type string /apps/metacity/global_keybindings/run_`basename $_A` "disabled"
Something like that. I have command 1 set to compiz deskmenu, so I wouldn't appreciate it if it was overwritten.
*/edit*
docter[~/tmp/tests] sh while-test-gconf.sh
command_2 is unset yet, will set it
docter[~/tmp/tests]
*edit-2*
Here are the patches:
postinst
http://omploader.org/vMjk5OQ
prerm
http://omploader.org/vMjk5YQ
apply with
patch -p1 postinst < postinst.patch
patch -p1 prerm < prerm.patch
This would bump 0.4.0-1 to 0.4.1-1
*final edit*
And here's the spec file included the source package I built it from.
Still for documentation purpose, and I couldn't test the package yet neither cause I currently don't have a test OS setup, but I'm gonna go for it the next few days.
I named it 0.4.1-1 but please don't release or try to do anything with this package, it's still only a draft.
Please look at it and read the files i included too bad. This is no replacement for the example package above, which basically is targeted on how the development directory structure could look like.
And this package only packs the binaries, would be nice if you could open all source files (maybe following the structure from the package above or so.)
Hope this gives you an idea what could, will and might be of importance if this project happens to grow further.
http://omploader.org/vMjlhaA
Adv Reply
(Do you know a good one)
Originally Posted by davim
Bookmarks