Bart,
I understand that this can be done either way. What I'm looking for is the best practice. If half of the packages use facets and the other half use extra packages, and a few use the faceted dependency, we'll have a mess.

Thanks.
Tom

Bart Smaalders wrote:
Tom Mueller (pkg-discuss) wrote:
Following up on the discussion of where source code would be a facet or a separate package (conclusion was separate package)...

Would test cases for a package be expected to be a facet or provided in a separate package?

The use case that is driving this question is MySQL, which has thousands of files that make up test cases that can be used to make sure that your server is installed correctly. In the current SVR4-based packages, there are separate packages (SUNWmysql51test, SUNWmysql5test).

It would seem that the definitive argument for source code (that one might want a different version than the binaries) probably would not apply in this case.

You can do this either way. You can also leave the package separate, but have a dependency on the test package w/ a facet to that it gets
installed only when the facet is enabled.

 - Bart



_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss

Reply via email to