Danek Duvall wrote: > On Mon, Mar 24, 2008 at 09:31:51AM -0700, Ethan Quach wrote: > >> What are the special provisions that would be needed to be handled by >> 'pkg' (or whatever software update mechanism is used) to enable the >> entire /var/share directory to be shareable across BEs? A couple that I >> can think of are: >> >> - a 'pkg remove' from any BE can't ever remove a package's contents from >> /var/share > > Unless it either removes the software from all BEs,
That's likely not going to be the case. We need to be able to support removing software from one BE and not another. > the target BE is the > last one on which the software is installed, I'm not sure how this would have any bearing. > or there's some mechanism to > say it's okay (e.g., the other BEs aren't used any more, but haven't been > deleted yet -- can a BE be "disabled"?). Right now there's no such mechanism. We could mount up every BE and check if the directory or file in question is registered in that BE. -ethan > >> - a 'pkg update' to any BE can't ever remove or change a package's >> contents in /var/share, but can only add to /var/share (change would >> include even simple changes like the permissions on a file or >> directory) >> >> - a 'pkg install' to any BE can't ever replace or change existing content >> in /var/share even if it conflicts with the what's being installed. > > Subject to the same relaxations as above, that seems appropriate. We > probably could find some mechanism to indicate compatible change in this > kind of data, but I'm having trouble thinking of change to this area of the > filesystem that isn't an install or removal, or happens very often at all. > > Danek
