Skip to content

Split out omicron-common dependencies #466

@pfmooney

Description

@pfmooney

At least one crate, propolis-server, is a dependency of omicron-common strictly for the purpose of being "available" to be built via cargo build -p propolis-server via the omicron-packager utility. This is a bit unfortunate, as it means the Propolis server, and all its dependencies are built when building anything else which depends on omicron-common.

It would be nice if propolis-server, and any other dependencies present (only) for the same reason were split out in some way so they didn't otherwise pollute the dependency tree.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions