response
slef: Krang doesn’t use PAR what it does is use m::b and throws everything into KRANG_ROOT’s lib directory. Unless things have changed for Krang 3.0 which too my knowledge isn’t the case. It seems this is the third or fourth time i’ve seen someone inquire about Krang’s build system but it doesn’t do anything special. The issue really should be handled higher up the food chain. The Perl project simply needs to come up with a good way to package their own programs. Past that, I haven’t done it myself with a perl program but Autopackage may prove useful.