Project ideas: packaging

Amitai Schlair edited this page Jul 15, 2014 · 2 revisions

The rump architecture allows unmodified userspace code to be built for a variety of target environments ("platforms") and provides a "hypercall interface" through which additional platforms may be relatively easily added. As with any layered architecture, each layer in the rump stack is generally intended to be dependent on lower layers and depended on by higher ones.


It would be nice to develop one layer of the rump stack without always having to rebuild all its underlying layers from source. In other words, it would be nice to have packages for components at each layer.

While pkgsrc/misc/rump has existed since 2009, it does not reflect current thinking on the proliferation of available components or current understanding of the boundaries between them.

As usual, solving the problem has at least two parts:

  1. Design: choosing logical boundaries between components
  2. Implementation: packaging components along these boundaries in at least one real package system

Trying to prepare packages, then trying to use them, will help us choose the right boundaries. Since pkgsrc shares contributors and interested parties with rump, and is no less cross-platform than rump itself, it's probably a good place to experiment with rump packaging.

Current thinking

It's likely that the following packages would, to a first approximation, suffice:

  1. Sources
  2. Tools
  3. Userspace headers (for building applications)
  4. Rump kernel components
  5. Hypercall implementations

Existing repositories and platforms

Clone this wiki locally
You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.
Press h to open a hovercard with more details.