Chris Quenelle wrote:
Here is an interesting and probably common scenario:
Let's say there's a large application which includes lots of
miscellaneous binaries
and scripts, which might not be used by most users. For example, let's
say it includes
a perl script in a 'demo' directory as an example of how to use a perl
API that it exports.
I'd have to agree with Brock here, if a package delivers a program, it
should also require any dependencies for that program to work. If the
average user doesn't need that program or the package causes undesirable
dependencies, then that program should be moved to a different package.
The only viable alternative in my mind would be to make the dependency
optional, and set it up so that if the optional dependency is installed
(either currently, or during the install process) the program also gets
installed.
Cheers,
--
Shawn Walker
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
