On Mon, Jun 08, 2009 at 11:07:10AM -0500, Shawn Walker wrote: > Bryan Allen wrote:
> >--force is not a cop-out; it is a tool, and a useful one at that, when you > >are > >under pressure to fix something. And not only, when one is under pressure, but too if an application is poorly assembled (snv has a lot of those pkgs) or/and would normally break your site policies, can't give you the freedom to "design" zones as one need them (big hint: package relocation), etc. . > Nevermind the number of times I had to go back to untangle the mess > someone had created on a RHEL system because they had used --force > because they didn't want to bother with the dependencies correctly. > > No thanks. Well, that's a weakness/problem of the packaging system. A good pkg system should be able to find out all unsatisfied dependencies as well as pkgs, which do not belong to the default SW clusters (and of course something like pkgchk [-v]) ... Just in case you need some examples: WARNING: SUNWgnome-vfs depends on SUNWsmbau, which is not selected WARNING: SUNWgnu-emacs-gtk depends on SUNWmlibl, which is not selected WARNING: SUNWgvim depends on SUNWmlibl, which is not selected S10: + WARNING: SUNWtexi depends on SUNWpl5u, which is not selected WARNING: SUNWjre-config depends on SUNWmozilla, which is not selected WARNING: SUNWevolution depends on SUNWmozilla, which is not selected samba: no separate server, client, docs/swat package mysql: no separate server, client, doc, test aka benchmark package *[jar]*: no separate doc packages (especially API doc overhead) ... So --force is something, what give's us the freedom we need!!! Regards, jel. -- Otto-von-Guericke University http://www.cs.uni-magdeburg.de/ Department of Computer Science Geb. 29 R 027, Universitaetsplatz 2 39106 Magdeburg, Germany Tel: +49 391 67 12768
