You can create an mxi file to pack the scripts into an Extension Manager installer.
Thank you Harbs. That seems to be exactly what I'm looking for.
I resuscitate this old topic because I'm personally facing major hassle dealing with "traditional" deployment methods - that is, manual installation and Adobe Extension Manager (AEM).
While I'm OK creating complex installers (signed, timestamped, hybrid, etc) apparently users are having all sort of troubles: AEM is not installed, AEM is not up to date, AEM has its period.
Adobe Add-ons (aka Exchange) relies on the Creative Cloud app File sync feature, which is error prone too.
Last but not least, manual installation is straightforward for some users, a pain in the neck for others.
To date, >95% of customer support emails I'm getting are for installation troubles.
Now, I'm not an ID guy but a PS one, I post here from time to time to (say hello to the ID people and to) learn how your community has solved problems that all Adobe developers might share.
My personal answer is to write installation scripts (which I'm currently testing) - using ExtendScript's Folder tokens and crossing fingers for CEP paths related to HTML panels (will that work on all locales?).
I don't know about ID, but PS can File > Script > Browse... (and load a JSX which duty is to copy/move files around)
Have you come up with different/better alternatives? How is your experience like?