want to know how slackpkg handles config files.are they removed with simple remove option or require any parameters?
Equivalent of purge in slackpkg or any pkg mgmt tool in slackware?

For a short overview see here.

For an in-depth explanation see there.

To know more if you have Slackware installed: man <command>

Also, all commands are shell scripts, so you can look into them to see how they work.

Main commands are: installpkg, removepkg, upgradepkg, pkgtool, explodepkg, makepkg, slackpkg.

1 members found this post helpful.

Upon invoking removepkg (which slackpkg does) you'll see warnings if certain items in the packing list are not removed. You can then just remove them yourself after.. redirect output to a file if your doing mass removes.

Since you're new, don't assume slackpkg to be 'omg holds my hand for everything'; its not comparable to apt.. it's just a simple front for pkgtools.

I personally don't even have it installed and just manually check changelogs (follwing stable), gftp the patches dir and `upgradepkg <dwl location>/*`.. then back up. I think its a good idea to have all source and tarballs backedup(especially if you dont have a complete install like me).

Although, it's probably smart to have slackpkg though, especially for it's template functionally.

/* Side note: of course, this also applies to any other packages you have installed 'unoffical' (slackbuilds.org, your own, ...).

If your curious how people ( well me ), manage their packages i can post my random `bash`ing for you to get an understanding */

Have fun with slack!

Now, to answer the actual question: There is no equivalent for the purge option in slackpkg, you have to remove config files yourself.
This is caused by the package managing system's way of handling config files and, IIRC, is not intended to change in the future.

1 members found this post helpful.

By the way, don't get the wrong idea about slackware.

All maintance is manually, of course there is `slackpkg` and `sbopkg` .. but that's only for their respected repos. if you would like to use software from any other location(ie: gnome -> dropline, mate, ...) these will not suffice:
{
slackpkg only supports 1 mirror and you wont find too many(if any) unofficial repos that have Changelogs and w.e other files slackpkg reads, in the style of mirrors mirroring ftp.slackware.com.
,
sbopkg deals with slackbuild tarballs in the style established by slackbuilds.org.
}

The point i wanted to get across now(and above mentioning i don't use slackpkg) is that in the end what these fronts give is very minimal, implying you should not expect to much and you can do everything with just pkgtools and bash(without too much more effort).

I do not know about purge, but in my understanding, removepkg will remove all files, including directories and symlinks, that installpkg did install (including configuration files), unless one of following conditions be true:
- have changed since installation,
- (directories) include new files/are not empty,
- are found in another package,
- are not found.

1 members found this post helpful.

You are right with that, but installpkg does not install the actual config files, it only installs the .new files. Those are removed/renamed later.
So at least the first condition is true, if the config files are also grouped up in directories the second condition is also true.

For example have a look at the content of /var/log/packages/slackpkg* :

1 members found this post helpful.

I didn't think about that, probably because I didn't have that broader picture in mind. Thanks, Tobi.

Wouldn't be too hard to do manually with something like:
Note: this doesn't take account of the fact that a file can be in multiple packages in slackware so it could do with tightening further.

Whether it'd be worth adding a --purge option to removepkg to do something similar or not I don't know, The odd unused config file doesn't do any harm, and it's easy enough to do something like the above yourself if you're really anal about leaving them about.

1 members found this post helpful.

rubankumars,
Start marking threads as solved