On Thu, Feb 08, 2007 at 02:58:16PM -0800, David Powell wrote: > > This is what pkg dependencies are for -- extend that to add versions and > > to tell pkgadd that these have to be upgraded together. > > Dependencies usually represent the functional needs of the software > delivered in them. Using/relying on a dependency to indicate that > file F moved from package A to package B between revs 3.1 and 3.2 > also seems semantically wrong (since there might not be an actual > functional dependency between the packages in either 3.1 or 3.2), not > to mention very difficult to maintain.
We'll need a way to deal with files moving from pkg to pkg if we'd use pkg updating. The details can be worked out, but, yes, it would be a pain to manage that kind of metadata. And that's a good point in favor of pkgrm + pkgadd. > > > Doing this with the existing tools (and a little help from everyone's > > > not-quite-public friend, /var/sadm/install/contents) is certainly > > > possible. Unfortunately, I think the ease of doing so has resulted > > > in the functionality not being sedimented into the packaging tools > > > where it belongs. > > > > But what tools do this? > > Solaris upgrade (in its various forms). Right, and those can depend on /var/sadm/install/contents. I was implying that with my question :) Nico --
