https://www.slackwiki.com/index.php?action=history&feed=atom&title=Doinst.sh 2026-04-08T16:09:24Z Revision history for this page on the wiki MediaWiki 1.40.0 https://www.slackwiki.com/index.php?title=Doinst.sh&diff=26&oldid=prev 2009-05-28T20:09:56Z

<p>Migrated from old wiki</p> <p><b>New page</b></p><div>This script is usually included under ./install within Slackware [[packages]] and contains post-install actions.<br /> <br /> Usually automatically created by [[makepkg]] for cleaning up and recreating symbolic links, advanced packagers may wish to include further configuration instructions here to be executed after files have been extracted from the .tgz package.<br /> <br /> == Files ==<br /> <br /> Within packages, doinst.sh is located in install/.<br /> <br /> After installation, the doinst.sh scripts are placed in /var/log/scripts, and renamed into the package name.<br /> <br /> == Examples ==<br /> <br /> === Handling symbolic links ===<br /> <br /> The package 'udev-064-i486-2' (from Slackware 10.2), contains a doinst.sh script which includes the following:<br /> <br /> ( cd etc/hotplug.d/default ; rm -rf 10-udev.hotplug )<br /> ( cd etc/hotplug.d/default ; ln -sf /sbin/udevsend 10-udev.hotplug )<br /> ( cd usr/man/man8 ; rm -rf udevsend.8.gz )<br /> ( cd usr/man/man8 ; ln -sf udevd.8.gz udevsend.8.gz )<br /> <br /> Thus, during installation of this package, it will delete 'etc/hotplug.d/default/10-udev.hotplug' and 'usr/man/man8/udevsend.8.gz', then immediately recreate them using symbolic links.<br /> <br /> This part of doinst.sh scripts is the most common, and is almost always generated by [[makepkg]] automatically during the creation of the package. In fact, 'makepkg' strongly suggests handling symbolic links using the doinst.sh script this way.<br /> <br /> === Configuration Files ===<br /> <br /> The package 'vim-7.0.109-i486-1' (from Slackware 11.0), contains a doinst.sh script which includes the following:<br /> <br /> config() {<br /> NEW=&quot;$1&quot;<br /> OLD=&quot;$(dirname $NEW)/$(basename $NEW .new)&quot;<br /> # If there's no config file by that name, mv it over:<br /> if [ ! -r $OLD ]; then<br /> mv $NEW $OLD<br /> elif [ &quot;$(cat $OLD | md5sum)&quot; = &quot;$(cat $NEW | md5sum)&quot; ]; then # toss the redundant copy<br /> rm $NEW<br /> fi<br /> # Otherwise, we leave the .new copy for the admin to consider...<br /> }<br /> config usr/share/vim/vimrc.new<br /> <br /> The config() function checks whether the configuration file in the package (vimrc) already exists on the system, or is exactly the same as the new one included in the package; if it exists and is not the same as the package's copy, it will not overwrite the old one but instead will be copied with a .new file extension (vimrc.new).<br /> <br /> This is a common, and the preferred, way of dealing with configuration files in Slackware packages.<br /> <br /> == See Also ==<br /> * [[Packages]]<br /> * [[Building A Package]]</div>

Dugan