Today's code review group has consensus, we'd prefer to see this as a separate resource.
If you want to discuss it further, the [chef-dev|lists.opscode.com/sympa/info/chef-dev] mailing list would be appropriate.
However, this action doesn't install the package in question, instead we're just installing the dependencies related to that package. While we're still working with packages here, this is a different pattern than just installing a package, possibly along with dependencies. That's what makes it different.
In other words, each resource should manage something specific. A package resource manages a package. Here we're managing the dependencies of a package, which I don't think is the same thing.