-   Slackware (
-   -   After slackpkg upgrade, (K)eep, (O)verwrite, (R)emove, or (P)rompt? (

papazulu 03-18-2013 06:56 PM

After slackpkg upgrade, (K)eep, (O)verwrite, (R)emove, or (P)rompt?
After running upgrade scripts slackware offers following. Which should I choose?:

Some packages had new configuration files installed.
You have four choices:

(K)eep the old files and consider .new files later

(O)verwrite all old files with the new ones. The
old files will be stored with the suffix .orig

(R)emove all .new files

(P)rompt K, O, R selection for every single file

What do you want (K/O/R/P)?

ponce 03-18-2013 07:05 PM

go for prompt and it will ask you for the modified files.

if you haven't customized anything you can overwrite the proposed file: if you are in doubt, select diff and see if you have made modifications that you want to preserve.

in the case you have customized the file you can delete the new one if it doesn't introduce new things/options: if it does maybe is better to keep it and re-customize the new later.

michaelslack 03-18-2013 08:21 PM

A good example where I got caught out here: I have been mucking around a bit with php. To get it working (just locally), among other things you uncomment out the line


Include /etc/httpd/mod_php.conf
in /etc/httpd/httpd.conf

Now recently there was a security upgrade of httpd in slackware-14.0 which I implemented using slackpkg and I wasn't careful and I ended up replacing my /etc/httpd/httpd.conf with a fresh new one, which of course had the line above commented out again.

This is the kind of thing to keep in mind at that stage of slackpkg!



zbreaker 03-18-2013 08:25 PM

If your running a conservative system, I've never gone wrong with the overwrite option for the upgraded packages.

All times are GMT -5. The time now is 09:28 PM.