------- Additional Comments From [email protected] 2005-04-07 14:10 -------
The point is: Init-script files can be edited by the user, maybe to setup some
things or modify the script. In order to make sure that this is retained when
e.g. an update is done, init scripts are marked as configuration files (do a rpm
-q -c on a package with init scripts to see this).
Applications should of cause "unregister" the init script by calling
"remove_initd", but when you do an update with a modified init script, the
foo.rpmnew points to the right binary wereas the foo init script, executed at
boottime, may point to the position of the previous release.
dpkg -r does not deinstall config files (and init scripts are config files),
only --purge does. (But remove_initd should ensure that init does not invoke
that script.)
rpm -e does not deinstall configuration files (only when) modified by the user,
they are renamed to .rpmsave
Conclusion: The test is useful in these cases
a) User-modified init script and update with different pathname to a neede
binary (in any case)
b) Deinstallation without purging on dpkg systems
c) Deinstallation with modified init script on rpm system
For b and c the user has to call them explicitly since they were deregistered
(remove_initd)
- - -
Purge is a concept of Debian/dpkg: If you simply do an uninstall, it leaves the
configuration files behind; only if you use the --purge option, they are
removed. rpm does by default remove all config files (except those modified by
the user).
- - -
Suggestion: Leave it as it is and only clarify the text. Maybe something along
this line:
"Init scripts shall not fail obscurely when they remain but the package has been
removed; this may happen since[or "when"?] they are marked as configuration files.
<footnote>
On dpkg-based systems this happens if the package is is not purged, with rpm if
they had been modified by the user; last not when least updating the package,
the user-modified init script may call a binary only present in the previous
version.
</footnote>
Therefore, you should include a test
statement at the top of the file, like this:
--
Configure bugmail: http://bugs.linuxbase.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
lmpx.com only provides a reader for public news (NNTP) servers. It is not
affiliated with the servers or forums shown here and is not responsible for
the content of articles, which is written by their respective authors.