----- [email protected] wrote: > Guys, > > Apologies for not keeping track but I was wondering if there is some > way to find out pkg dependencies on kernel components in recent > times. > Specifically, if I am running b136 or b137, how far up can I go just > for pkg components.
It's difficult to say. There have been changes in libbe, Python, and other components that pkg(5) depends on. The only way I know of is to try it and see what works. > And separately, did we ever implement a force install? i.e. forcing > a pkg to install even if the dependency check is not met. Basically > for people who know what they are doing and know the dependency is > wrong/obsolete. A package manager can't manage packages if the dependency graph is broken. It is highly unlikely that a force option will ever be implemented. If you have a broken package, then your best option is to use pkgrecv to retrieve it, use pkgmogrify (or a text editor) to remove the dependencies you don't want from the manifest, and then use pkgsend publish to republish it to your own repository. That's far more maintainable. -Shawn _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
