On Thu, 05 Jan 2006, Steve Langasek wrote: > > > > BUT, if you do, don't ship /var/run inside the deb. > > > Why? > > > Because: > > > 1. It will go away on reboot and if your service isn't enabled, it won't > > be re-created. dpkg will still think it should be there, however. > > And what does that break? AFAIK, dpkg will ignore a missing directory on > package removal without incident.
Well, it is not good form. If you want to ship it there, be my guest. But don't expect me to tell others to ship it _unless_ there is a real reason to do so, and so far there isn't (there might be one in the future). > > 2. We may deploy some auto-create-stuff-in-/var/run solution, and it WILL > > clash with packages that ship /var/run and recreate it (not that I'd > > expect that clash to do anything other than mkdir -p be a waste of > > time -- but better safe than sorry). > The /var/run directory itself *must* always exist; it has to be on the > filesystem which holds /var. Yes. But that has nothing to do with packages shipping stuff inside /var/run (plus /var/run itself), does it? > > Also, it makes life easier for us to track down packages that need to be > > examined for lack of ephemeral /var/run support. > > I think you're going to need a more reliable test than this. Probably. -- "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]
