in reply to Re: Packaging multiple use statements into a module
in thread Packaging multiple use statements into a module

There are two problems with Toolkit that I see. First is that it uses a source filter to do its work, and that is almost guaranteed to become a problem eventually. Second is that it is meant to load one set of modules that are defined per-machine.

I think ToolSet is generally a better choice. In addition to not using source filters, it is meant to build your own modules for including groups of prerequisites. Being based on modules like this instead of a single per-machine list makes it redistributable as well.

  • Comment on Re^2: Packaging multiple use statements into a module

Replies are listed 'Best First'.
Re^3: Packaging multiple use statements into a module
by djerius (Beadle) on Feb 09, 2010 at 17:26 UTC
    After looking at ToolKit I've come to the same conclusions that you have. Thanks for pointing out ToolSet — it's much more along the lines of what I want. And it has the added benefit that I think I understand what it's doing!