Brock Pytlik wrote: > * source - This contains the file or service which needs the target. > (This is equivalent to pkg.debug.depend.reason in generated > dependencies.) This can be specified more than once. Each file or service > provided must be delivered in the same manifest as the dependency.
I'd rather not require source or reason attributes -- I think it raises the barrier to using this construct sufficiently that either people will put in useless data (reason="because I said so") or they simply won't use it, which I think would be sad. I do think it'd be appropriate to have pkglint support for enforcing the use of it, though, so we can make sure that folks contributing to Solaris consolidations do use it properly (with code reviewers and RTI advocates making sure that silly reasons aren't used). > Should we keep kind, or should target and source just use schemes to > identify the kind of thing they're referencing? I'd lean towards merging kind and target and simply requiring a full FMRI and assuming a file path if there's no scheme. > Do we need to allow users to specify path and basenames separately > (like generate does) or is allowing multiple full paths sufficient? > Can target be a relative path to source? Do you have a use case for either? Danek _______________________________________________ pkg-discuss mailing list pkg-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
