> However, one problem with this is that it creates a situation where > you are publishing a package that depends on a file in a package that > hasn't been published yet.
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. 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. -j _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
