On Thu, Feb 2, 2012 at 9:05 AM, Nicholas Clark <nick@ccl4.org> wrote: > On Thu, Feb 02, 2012 at 09:41:36AM -0500, David Golden wrote: >> On Thu, Feb 2, 2012 at 8:10 AM, Nicholas Clark <nick@ccl4.org> wrote: >> >> > because perl already splits @INC to core / vendor / site, in different >> >> > directories (and that's awesome). there's unfortunately only one bin >> >> > directory. :-) >> > >> > But that's somewhat hard to solve, as the perl binary defines where @INC >> > is (and can split it apart into as many directories as are needed), whereas >> > the user's PATH determines which binaries are found. >> >> I think it's "solvable" for vendor needs if we can more clearly >> identify which scripts come from core and which come from dual-life >> modules. Right now, they're all jumbled in utils/. > > Aye, but I think that getting them out of there cleanly depends on > untangling how VMS does its .com wrapping, and putting it in the same place > (structurally) as the Win32 pl2bat wrapping. With that done, they sit very > nice I think that untanglement is done: <http://perl5.git.perl.org/perl.git/commitdiff/5844a3edbd3499c6a146436e1d7ec0648feacb5b> Other than that I think VMS would need essentially the same changes as other platforms, though we won't know for sure until we try it.