Dist::inkt itself does virtually nothing; it creates an empty directory, generates a manifest file, and then wraps it all up into a gzipped tarball. but it provides various hooks along the way for subclasses to grab hold of. so the general idea is that you write a subclass of dist::inkt, which consumes various moose::roles to do the actual work of populating the distribution with files.

as such, dist::inkt is not so much a distribution builder, as it is a framework for writing your own distribution builder.

several roles of varying utility are bundled with dist::inkt, as is dist::inkt::profile::simple, a subclass of dist::inkt which consumes most of these roles.