On 04/13/11 10:01 AM, Shawn Walker wrote:
----- [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.
Somehow I had a feel that you were going to say this :) I was still
hoping that someone might have tried it out and have some more data
points.
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.
Its mostly for 3rd party/contrib packages that you need a force option.
Some of them were created with no reason for a dependency to be there
or somehow ended up specifying a particular build etc. These are mostly
leaf packages. But I see your point about using pkgmogrify.
Thanks,
Sunay
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
