Petter Reinholdtsen wrote: > How do you believe insserv should behave when it encounter two > packages with different dependencies and the same provides header? > What dependency three should it build? I'm not sure, so I decided to > reject such configurations until it was clear to me.
I suppose that that is not a well-defined situation. The safest bet would be that a service that requires or should start after, say, postgresql, should start after all of them. The duplicate services themselves could start at different positions. For example, a future postgresql-8.4 might suggest to start after avahi, so it would start much later than the current postgresql-8.3. But that's OK. But then any serivce that is supposed to start after postgresql would have to be reordered to start after postgresql-8.4. In fact, I just tried this out, and insserv handles this perfectly. If you want to try it out, install avahi-daemon, postgresql-8.2, postgresql-8.3, and slony1-bin. Then add Should-Start: avahi to postgresql-8.3 and do /usr/sbin/update-bootsystem-insserv. You will see how postgresql-8.3 moves down and slony1-bin with it, but postgresql-8.2 stays where it was. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
