| Subject: | [WISHLIST] Sharable and self-documenting toolkit profiles |
A big limitation of Toolkit is that Toolkits live only on your machine. And they are not self-documenting. How about something like:
use Toolkit http://somesite/conway.plt
where "conway.plt" looks like:
use strict;
use warnings::register __PACKAGE__;
use Carp;
no Carp::Assert;
use Smart::Comments;
require Exporter;
Basically a "plt" file will have only "use", "no" or "require" and Perl comments. Nothing else allowed.
Toolkit would cache the file. Maybe once a certain interval (unless forced) it would check for updates.
Toolkit could even be made smart and install prerequisites for you.
If I run across a script, I can look up the URL to see what it uses. Utilities such as Module::Build could include the profile (whether it's shared on the internet or lives only on my machine) in the distribution.
The advantages of these changes are that profiles are shared, and some can even become standard... perhaps they can be hosted on CPAN or FreePAN.
Cheers!
Rob