| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When admins choose to allow slackpkg new-config to overwrite
currently installed config files with the .new counterparts
from an upgraded package, slackpkg has traditionally created
backups of the config files first, with the backups being
written out with .orig extensions. This commit does not change
the default behavior, but it does allow it to be turned off.
TLDR: set "ORIG_BACKUPS" to "off" in /etc/slackpkg/slackpkg.conf
if you do not wish to have .orig files left over
Signed-off-by: Robby Workman <rworkman@slackware.com>
|
|
|
|
| |
Signed-off-by: Robby Workman <rworkman@slackware.com>
|
| |
|
| |
|
|
|
|
| |
Thanks to Eduard Rozenberg.
|
| |
|
|
|
|
| |
Thanks again to burdi01 on LQ.
|
| |
|
|
|
|
| |
Essentially, don't process a "not yes" as an "is yes"
|
|
|
|
|
|
|
|
| |
Existence of /etc/lilo.conf coupled with executable /sbin/lilo
probably indicates lilo usage on the system, so that seems like
a reasonable compromise for everyone fussing about slackpkg's
offer to run /sbin/lilo for them after kernel upgrades even
though they use grub or whatever else.
|
|
|
|
|
|
|
|
| |
** This was my mistake; my mail client munged the patch, so
I had to apply it all by hand. The extra (old) line of
'showmenu' options was what I'd copied to compare the
new options, and I forgot to delete it when committing.
Mea culpa. --rworkman
|
|
|
|
| |
Signed-off-by: Robby Workman <rworkman@slackware.com>
|
|
|