SLKBUILD douninst?

[Ali82]

Hello,

I'm slowly moving to Salix, escaping from the very fast moving Arch that keeps my machine a test field. However, I build a lot of package myself, using makepkg and PKGBUILD under Arch, probably was the only thing that kept me running this system for such long time.

Now, I was wondering if there is a way to execute commands after package removal? Like doinst but a douninst.

Thanks.

[ChuangTzu]

You are moving from one end of the spectrum to the other. Salix/Slackware is the most stable.

You can use "slapt-get -remove" to uninstall repo packages and "spkg -d" to remove packages that you build from source outside of Salix repos.

We have "slkbuild"which is similar to Arch's pkgbuild, so you will feel right at home there.

These links will help:
http://guide.salixos.org/31PackageManagement.html#4_1
http://guide.salixos.org/32Packagemanag ... e.html#4_2
http://guide.salixos.org/324spkg.html#4_2_4
http://guide.salixos.org/325MakingaPack ... html#4_2_5
http://docs.salixos.org/wiki/index.php/ ... h_slkbuild

[Ali82]

SLKBUILD files have the doinst() functions to execute commands when a package is installed. But I don't understand why it does douninst to execute command after package removal.

[gapan]

No, there is no such thing. The restriction comes from Slackware package management as there is no provision for such files there, it's not a restriction of SLKBUILD. And to be honest, it's not much of a restriction anyway. In theory, it sounds useful, but there is very little actual use for such a feature. The only thing that gets left behind after removing a package could only be settings files in /etc, which you probably want to keep, in case you reinstall the package and don't want to configure its settings all over again.

What do you want to do that would require a douninst?

[Ali82]

What do you want to do that would require a douninst?

Update font cache, icon cache, mktexlsr? to name a few.

[mimosa]

Try update-all (its manpage tells what it does).