you probably can't change mid-stream now, but my point was that because the custom modules sit separately and are architecture agnostic(?), we had merely a tar archive of the custom modules. so didn't need to make .msi, .dep, .rpm, etc.
as for the main embedded perl distribution. that was also essentially a .tar archive, with a little bit of installation script that worked across all platforms...because on windows we had cygwin. All in all, for the server side of things for install or major upgrade there was one package for linux, one for unix (only some internal differences to linux), and windows. But all of these followed same pattern of using least common denominator (e.g. tar) to achieve desired outcomes. The install/upgrade script was exactly the same for all platforms. the only real difference between the distributions was that because the install/upgrade couldn't assume cygwin & perl were installed, so for windows these were bootstrapped into the .exe. also the data api commands and server daemons were pre-compiled, so this /bin directory was different for linux/unix/windows.