Scratch
archived forums
#1 2009-10-15 16:26:11
Installation on Debian Lenny
I installed scratch_1.4.0.debian.5_i386.deb on a Debian Lenny. An error was displayed at the end of the installation. The post installation script tried to access to /etc/gnome/defaults.list but this file is located at /etc/gnome-vfs-2.0/ on my computer. Scratch runs well in spite of this error. I put a link to the defaults.list in the folder /etc/gnome/. So, for an perfect installation on Debian Lenny, add a link in the folder /ect/gnome or make some changes in the scripts postinst and postrm see http://my-trac.assembla.com/scratchonlinux/browser/debian
A great software program
Offline
#3 2009-10-16 16:51:16
Re: Installation on Debian Lenny
pathua wrote:
I installed scratch_1.4.0.debian.5_i386.deb on a Debian Lenny. An error was displayed at the end of the installation. The post installation script tried to access to /etc/gnome/defaults.list but this file is located at /etc/gnome-vfs-2.0/ on my computer. Scratch runs well in spite of this error. I put a link to the defaults.list in the folder /etc/gnome/. So, for an perfect installation on Debian Lenny, add a link in the folder /ect/gnome or make some changes in the scripts postinst and postrm see http://my-trac.assembla.com/scratchonlinux/browser/debian
A great software program
Interesting! I wonder if there is a utility of some sort we could use, or perhaps some sort of defined path, that would choose the right location based on the system. That way it would work on Ubuntu or this version of Debian. If you have any ideas, let us know - perhaps you could submit a patch?
Help Scratchers make the leap to 2.0!
Offline
#4 2009-10-22 17:38:53
Re: Installation on Debian Lenny
After reading some documentation about how to build a debian package, I think that the problem is somewhere in the file rules. See http://www.debian.org/doc/maint-guide/ch-dreq.en.html#s-rules. In this file, I think that the line dh_installmime can solve the problem. In this case, the postinst and postrm script are automatically build. An example of the postinst scripts from the carmetal program:
#!/bin/sh
set -e
# Automatically added by dh_installmenu
if [ "$1" = "configure" ] && [ -x "`which update-menus 2>/dev/null`" ]; then
update-menus
fi
# End automatically added section
# Automatically added by dh_installmime
if [ "$1" = "configure" ] && [ -x "`which update-mime 2>/dev/null`" ]; then
update-mime
fi
# End automatically added section
# Automatically added by dh_installmime
if [ "$1" = "configure" ] && [ -x "`which update-mime-database 2>/dev/null`" ]; then
update-mime-database /usr/share/mime
fi
# End automatically added section
# Automatically added by dh_desktop
if [ "$1" = "configure" ] && which update-desktop-database >/dev/null 2>&1 ; then
update-desktop-database -q
fi
The man page of update-mime says that the packages need to create a file in the /usr/lib/mime/packages directory. An example of this kind of file from the carmetal program
application/x-carmetal; carmetal '%s' ; edit=carmetal '%s' ; test=test "$DISPLAY" != "" ; description="CaRMetal figure" ; priority=2
If I compare the scratch.list with carmetal.list, carmetal has these lines more
/usr/lib/mime
/usr/lib/mime/packages
/usr/lib/mime/packages/carmetal
I hope this will help you. May be there are some mistakes because I am not a developer.
Offline