Ben Collins <[EMAIL PROTECTED]> writes: > Heh, restart display managers is outside the scope of libc. Restarting > services is pushing it enough I think.
Hmm, I wonder if it would be saner to have some mechanism (perhaps just a directory fed to run-parts?) for packages to register themselves for the next time this sort of change happens; having libc list affected services itself does strike me as a layering violation. OTOH, such events seem pretty rare (yay for compatibility within minor versions), so adding extra infrastructure for them may be overkill. On the gripping hand, Debian has always (rightly) placed a lot of value on infrastructure AFAICT. Thoughts? (Obviously this is too late to use for 2.2 -> 2.3, but it should be possible to complete the transition in plenty of time for whatever follows it [2.4? 3.0?].) -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) Finger [EMAIL PROTECTED] (NOT a valid e-mail address) for more info. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
