Consider the case where package a...@1 and a...@2 depend on b...@1, and b...@2 is in the repository, and a...@1 and b...@1 is installed.
pkg install a...@2 doesn't install b...@2 today. So you can do the test you describe below without the --nodeps option. The key here is that every package should express its dependencies correctly. If a...@2 really only depends on b...@1 and not b...@2, then it should state the dependency that way. Tom jan damborsky wrote: > I can see this feature would be also useful for developers. > > For instance, if I would like to test that package containing > bug fix delivers things correctly on target system. Then > I would do following in order to make sure all dependents > are left untouched: > > # pkg uninstall --nodeps original_package > # pkg install --nodeps modified_package > > The same could be used for testing backward compatibility, > when I would like to test how new version of package > delivering bug fixes will behave on the oldest system > to be supported before that package is backpublished. > In this case, I intentionally want to avoid installing > newer versions of all dependencies involved. > > Jan > > _______________________________________________ > pkg-discuss mailing list > [email protected] > http://mail.opensolaris.org/mailman/listinfo/pkg-discuss > _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
