On Mon, 26 Jun 2006, Lars Wirzenius wrote: > The bug is about a full path to policy-rc.d, not invoke-rc.d. The only > place I can find that uses policy-rc.d is invoke-rc.d, so I don't think > we need to worry about anything else calling it.
Err, sorry, I got confused. Well, yes, we could remove the path from invoke-rc.d, as long as we coordinate that with other invoke-rc.d's, and there are few enough (two, three?) that it shouldn't be a problem. Whether that will gain you anything depends on nothing else mucking with the PATH, though. And given that we are talking maintainer scripts here, I am not really sure what to expect. I am not at all opposed to removing the policy-rc.d path, *but* it should be handled as a minor specification change (there will be documentation to be updated, and other packages that provide invoke-rc.d, mainly file-rc and friends, need to be checked for compliance). -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
