Tom Mueller (pkg-discuss) wrote: > 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.
I have tried, but it doesn't seem to work in this way: # uname -a SunOS tio-nb 5.11 snv_101b i86pc i386 i86pc Solaris # pkg set-authority -O http://10.18.138.30:10106 opensolaris.org # pkg search SUNWinstalladm-tools # pkg search -r SUNWinstalladm-tools INDEX ACTION VALUE PACKAGE legacy_pkg legacy SUNWinstalladm-tools pkg:/[email protected] legacy_pkg legacy SUNWinstalladm-tools pkg:/[email protected] # pkg install SUNWinstalladm-tools Creating Plan | pkg: The following pattern(s) did not match any packages in the current catalog. Try relaxing the pattern, refreshing and/or examining the catalogs SUNWinstalladm-tools # pkg install pkg:/[email protected] Creating Plan | pkg: the following package(s) violated constraints: Package pkg:/[email protected],5.11-0.106 conflicts with constraint in installed pkg:/entire: Pkg SUNWinstalladm-tools: Optional min_version: 0.5.11,5.11-0.101 max version: 0.5.11,5.11-0.101 defined by: pkg:/entire # pkg list entire NAME (AUTHORITY) VERSION STATE UFIX entire 0.5.11-0.101 installed u--- > > 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. That would be the ideal case. But this is apparently not something which will be solved soon and once forever. The mechanism to handle such cases (when dependencies are not set correctly or are in process of being resolved) is needed. Jan > > 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
