[email protected] wrote:
We're not preventing you from doing your job, we're trying to prevent you from building a broken default configuration.
Pkg A contains a hardlink to a file in pkg B, and has a require dependency on pkg B as a result. If pkg A is installed with --nodeps, and package B is not installed, what should happen? This packaging system is designed to support the installation of software according to the parameters laid down by the publisher. The design of variants and facets, for example, is driven by the need of the publisher to specify the supportable alternative configurations of his/her product; the removal of arbitrary portions of a package (including dependencies) at the whim of the administrator can and _will_ produce arbitrarily broken results. Administrators seeking to redesign packages to better match their notion of an ideal distribution should republish the packages to match their requirements; of course, the results will not likely be supported by the originators of those packages. - Bart -- Bart Smaalders Solaris Kernel Performance [email protected] http://blogs.sun.com/barts "You will contribute more with mercurial than with thunderbird." _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
