> > How is this any different from the behavior that we have today? I can > > write a package with a dependency on a package that isn't in the > > repository. At least in the current code, we don't require that that the > > dependent packages be present in the catalog. > > It is different because the server won't have the information > necessary to tell you which package provides the file.
This is true only if you assume that the server has to be able to figure this out and that it cannot fail. In a previous post you observed that for the case where many or no packages are found to match, we should fail. In such a case, the developer who is publishing the package must specify the pkg dependency explicitly. > > We're talking about a mechanism that allows the developer to > > specify a file name, and if possible, get that translated to a package > > dependency. This needs to happen at publication time; however, it would > > make more sense to have the publication client (pkgsend, solaris.py, > > whatever), and not the server, figure out the dependency. > > Yes, that is what I was pondering. This is how it works today. The publication client is the one figuring out the package dependencies. -j _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
