OpenPKG CVS Repository
http://cvs.openpkg.org/
____________________________________________________________________________
Server: cvs.openpkg.org Name: Thomas Lotterer
Root: /e/openpkg/cvs Email: [EMAIL PROTECTED]
Module: openpkg-re Date: 23-Jul-2003 14:03:17
Branch: HEAD Handle: 2003072313031700
Modified files:
openpkg-re upgrade.txt
Log:
considerations regarding rc; braindump of more points
Summary:
Revision Changes Path
1.3 +48 -1 openpkg-re/upgrade.txt
____________________________________________________________________________
patch -p0 <<'@@ .'
Index: openpkg-re/upgrade.txt
============================================================================
$ cvs diff -u -r1.2 -r1.3 upgrade.txt
--- openpkg-re/upgrade.txt 23 Jul 2003 08:19:12 -0000 1.2
+++ openpkg-re/upgrade.txt 23 Jul 2003 12:03:17 -0000 1.3
@@ -8,7 +8,54 @@
Upgrade from OpenPKG 1.2 to OpenPKG 1.3
=======================================
- o rc_all/rc_def
+ o the rc variable "openpkg_runall" was renamed to "openpkg_rc_all".
+ Presence of the obsolete variable is detected, a warning is printed
+ and the value of the obsolete variable overrides the newly
+ introduced variable, if both exist. The meaning remains the same.
+ It controls whether a "rc all ..." instruction will run anything or
+ not. Note the bootstrap uses "rc all start" and "rc all stop" on
+ system boot and shutdown so this effectively enables or disables the
+ automatic boot and shutdown of all daemons. This does not affect any
+ use of "rc" with a specific package being named.
+
+ o the rc variable "openpkg_rc_def" is new and it sets the default for
+ enabling or disabling rc sections for a package, as all packages use
+ a "FOO_enable=${openpkg_rc_def}". This allows control of all
+ packages at once.
+
+ o the rc variable "FOO_enable" for any package can be overridden in
+ the "rc.conf" file to enable or disable rc sections for a specific
+ package. This works identical to previous versions. However, with
+ the new "openpkg_rc_def" the default for all "FOO_enable" variables
+ omitted from "rc.conf" can be controlled now. This means it is now
+ possible to default to "no" and only launch certain applications or
+ default to "yes" and inhibit certain applications. Also keep in mind
+ that the execution of sections from "all" packages is additionaly
+ controlled by the "openpkg_runall" variable.
+
+ o packages containing services to be run in the background now
+ consistently provide "start", "stop" and "restart" sections. Some
+ also provide a "reload" section.
+
+ o A new section "status" was created which allows for querying
+ information about the status of a package, namely "enable",
+ "useable" and "active". The output format is in bourne shell
+ variable assignment syntax so it can be eval'ed from scripts. It's
+ also human readable. A package is enabled if it's effective value
+ of "FOO_enable" is set to "yes". Some (few) packages have config
+ checkers and usable means they're ready to launch. Many packages
+ return "unknown" here. A package is active when it's daemon is up
+ and running.
+
+ o FIXME
+ - check anything listed here must be moved to NEWS or vice versa
+ - removal of /var files including logs on erase
+ - restart of application on startup
+ - inhibit rc ... start if .rpmsave found ...
+ - default daemons to listen on localhost (no wildcards, except amd/ntp/openssh)
+ - fsl optional, defaults to yes; append=1 vs. trunc=0; jitter=1
+ - linters (i.e. use rclint for opServiceEnabled vs. rcService)
+ - %{l_value}
o coreutils
@@ .
______________________________________________________________________
The OpenPKG Project www.openpkg.org
CVS Repository Commit List [EMAIL PROTECTED]
