FS#9879 - [initscripts-splash] Backup significant /etc/rc.* scripts

Attached to Project: Community Packages
Opened by Ray Rashif (schivmeister) - Wednesday, 19 March 2008, 14:40 GMT
Last edited by Roman Kyrylych (Romashka) - Saturday, 05 April 2008, 09:00 GMT
Task Type Bug Report
Category
Status Closed
Assigned To No-one
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Issue:

My sysinit script is extensively modified to fit my requirements and it just got replaced. I'm pretty sure I'm not the only one with custom init scripts so /etc/rc.{sysinit,single,shutdown,multi} should be included in the list of files to backup.

I didn't bother about backing them up myself as I'd presumed the packager would do that with all of those that are important, because they _are_ critical system files after all. I understand I should've first looked up what files it _does_ backup, but I believe that if we want to have a particular feature we should have it do what it's supposed to - properly. We could go on and on about different ways to prevent such mishaps, but that isn't the point.

Package:

initscripts-splash 2007.11-1
This task depends upon

Closed by  Roman Kyrylych (Romashka)
Saturday, 05 April 2008, 09:00 GMT
Reason for closing:  Not a bug
Comment by Ray Rashif (schivmeister) - Wednesday, 19 March 2008, 14:46 GMT
For the sake of code:

backup=(etc/{inittab,rc.{sysinit,conf,local,local.shutdown,single,shutdown,multi}})
Comment by Roman Kyrylych (Romashka) - Saturday, 05 April 2008, 08:59 GMT
initscript files are not intended for customization and thus are not (and won't be) backed up in initscripts{,-splash}
( == your custom initscripts changes will be lost with official initscripts upgrade too)
The correct way to avoid breakage is to add any non-config scripts you modified to pacman.conf,
e.g. NoUpgrade = etc/rc.sysinit

Loading...