The managed dependencies are tracked in a *carton.lock* file

Somehow that doesn't sit right with me :)

Sure, the tool is called carton, but .lock doesn't exactly convey managed dependencies, and carton doesn't exactly convey managed dependencies

And then, you have to use

cpanp z Foo
...
carton install
[download]

First time I had to do this, I created a Bundle::

When Task came out, so I created a Task::

Once I included the tarballs with Module::Install::Bundle

Other times I just call cpanp , local::lib-style

I might appreciate carton more once I turn to steam and land in the cloud :)

I do understand, this being from miyagawa, has a real use-case in mind, and being inspired by popular thing, it will probably be filled with lots of steamy pop goodness

So as miyagawa says, I'm probably going to keep doing what i'm doing, and that is just fine :)