Chris Quenelle wrote:
Brock Pytlik wrote:
> If, instead, you're asking for overrides for specific dependencies,
like pkgsend claims you must depend on a, b, and c, and the package
maintainer is has to add "undepend a" "undepend b" and "undepend c" to
their manifest, then I have slightly less concern. I still don't like
the idea though.
Just to be clear, that's exactly what I was suggesting. It would only be
used if the package supplier determined that one of the automatic
dependencies was incorrect. Since I have no immediate problem that needs
solving here, I don't have a real stack in this at the moment. I just
wanted to raise the issue. It seems easy enough to add an "undepend"
feature later if this becomes a problem.
That's pretty ugly. I'd just as soon that dependencies are not
automatically added unless that behaviour is asked for. There's too
many chances for whatever dependency "plug" is in place to get things
wrong. I'd rather the automatic dependencies be handled as a warning or
as a suggestion system.
There's also a question of ambiguous dependencies.
For example, if the #! line contains /usr/bin/python, does the program
depend on python 2.4 or python 2.6 or the latest version in the repository?
--
Shawn Walker
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
