Onno Molenkamp wrote: > Currently, distro-import seems to include obsoleted packages in a > consolidations incorporation. This means that for software that has been > obsoleted in Solaris, like PostgreSQL, it's impossible to install > packages from an alternate repository using the same name. (unless they > happen to have exactly the same version as well) > > I can see the point of constraining software to certain versions using > incorporations, but is there any point in doing this for packages that > explicitly -don't- include any software anymore?
The point is to coerce the system to remove the software on upgrade once the software is considered obsolete. I agree that the decision to force obsoletion of components of SFW is probably not what's desired, but even correcting that, there's no way to override the version incorporated. For instance, I'm trying to figure out the best way of having a test version of mercurial on my system at a different version. It's not possible without also rewriting the incorporation that constrains it (sfw-incorporation). The bug there is that it's incorporated at all. Mercurial (in my case) shouldn't have any constraints on it (except perhaps by plugins that we might, but don't, deliver). Likewise with postgres, though there there's likely a cluster of packages that should be constrained together so that they're delivered in a consistent fashion. The in-progress userland consolidation is planning on removing these over-constraining incorporations, but that probably won't happen for a while yet. Danek _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
