Use of rcorder for local rc.d/*.sh scripts

[Doug Barton]

I've been following this discussion with interest, and I think that Brooks
is right about not having a flag day. On the other hand, I have seen many
people say that they want to get the ports rc.d scripts integrated into the
main rcorder, since some of their software "needs" this functionality. This
will become increasingly important as we move to modularize the base more
and more (ala BIND and openssl).

So, what about this for a compromise? We continue running localpkg to handle
the 000.*.sh and such, with JR's hack to incorporate those better. But we
ALSO build in the functionality to the main rcorder implementation to handle
scripts that do not have *.sh, and we require port authors to include a
special keyword in the script so that rc.subr will know that it is "safe" to
handle them this way. Once the transition is "complete," we drop processing
of the keyword, and the port authors can remove it at their leisure.

Thoughts?

Doug

-- 

    This .signature sanitized for your protection