Bug#427499: Merge a few bugs and provide LSB header

[Petter Reinholdtsen]

[Andre Felipe Machado]
> The Should-Start: $all is supposed to be a weak dependency, a
> desired order that will not cause a failure if not satisfied.

I believe this is a misunderstanding on what a weak dependency is.  A
weak dependency mean that it will not fail to register/install this
script if the dependency is missing.  If it is present (all $all
matches all/any script, thus always present), the script have to start
after and stop before its weak dependency.  If it can't, the ordering
is not well defined.

> I imagined that when the init installer, at "first pass", will try
> to move each script to the end of queue as per weak dependency spec,
> then, at "second pass", will try to satisfy the strong dependencies,
> correctly ordering all.

The current implementation of insserv will first order all scripts
according to their dependencies ignoring the $all, and finally move
all scripts with the $all dependency to the last order + 1.

> My first guess was to specify strong dependencies $remote_fs and
> $network for all packages.
> 
> But then realized that each script will depend on previously started
> other and only the first (ccs) should have such strong dependencies.
> Specifying strong dependencies almost equal to all scripts, may
> confuse the installer order resolving.

Yes, if the packages have hard dependencies on each other and can know
that other scripts will be installed in time, it can drop the
$remote_fs dependency.  I would not recommend it, though, as it
document the need for a mounted /usr/ and it is useful to include in
case the script dependencies are changed in the future.

> I am not sure if the installer could accomplish such task, yet. 

The dependency based boot sequencing system insserv that is used in
Debian handle this just fine.

> If the DD could make things easier to the installer, the better.
> 
> As the redhat-cluster-suite should install all init.d scripts, these
> headers should be enough to guarantee consistency.

I trust you there. :)

> Also, I am not sure about needing the non-standard Debian and Suse
> custom headers for reverse dependency, given that the package will
> install all scripts.

They are probably not needed in this case.  They have proven useful in
other cases.

Happy hacking,
-- 
Petter Reinholdtsen