Brock Pytlik wrote:
Step ??) Allow dependencies to be expressed on files, groups, users, and links, instead of on packages and have either the client or the depo do the conversion at publication time. (Labeled as ?? since I'd like to do this client side as part of step 1 but I want to keep the wads of reasonable size and I think there may be some complixity with this idea and creating new mutually dependent packages which express their dependencies in this manner.) This is roughly what I think of when we've talked about publishing against an incorporation in the past.
Another wrinkle with automatic dependency verification that occurred to me is that some software distributes dependencies within the same package.
For example, what if one of the detected dependencies is provided for by the product itself? For example, python scripts can be run with Jython. Another example might be a custom version of an existing open source library distributed with the software itself.
There's also the issue of ambiguous matching with dependencies, where more than one possible match exists. If I declare a dependency on a particular file, but that file is provided for by multiple packages, that renders the dependency declaration useless.
Furthermore, as (or if) the list of possible software sources to validate against is changed after earlier packages are published, it is possible that the resulting generated dependencies might change causing inconsistency between packages that were published earlier and later.
Cheers, -- Shawn Walker _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
