# New Ticket Created by Will Coleda # Please include the string: [perl #56382] # in the subject line of all future correspondence about this issue. # <URL: http://rt.perl.org/rt3/Ticket/Display.html?id=56382 >
I wanted to open a new ticket on this so discussion regarding how we get this in place for smolder is separate from smolder itself. The most expedient solution to getting this working is to simply bundle TH3 with parrot, as we do for other non-core modules we must rely on. I am wondering if it would not be better to more specifically declare our dependencies so we can avoid backsliding on our goal of eliminating CPAN modules from our repository. We have the following types of parrot builders: 1) Those that install from CPAN. This means a pretty trivial dependency listing. 2) Those that install from a package The package builder already has to depend on perl, they can depend on other modules as well. 3) Developers We already have Bundle::Parrot for developers; moving another item into that Bundle shouldn't be an issue. 4) ... everyone else. For someone grabbing a version of parrot off the website (especially if we ever host them away from CPAN) isn't going to have any easy hooks for following dependencies. However, we can just add this as a probe during Configure.pl; if we find any dependencies that are not available with the perl we're running as, we can print out a nice, helpful diagnostic about the minimum required version of the module. (I recommend a single probe that checks for all the perl dependencies for the build. If any modules required for building are missing, die. If any modules used in testing are missing, only warn, and conditionalize all the tests to handle the lack of the module gracefully.) (This step would probably have to be one of the first steps run, since I see File::Which is used during configure.) -- If we went this route, we could avoid including T:H3, and also remove any of the remaining modules we bundle in lib/ Comments? -- Will "Coke" Coleda
