I use the noCPAN tarball, as I keep all of the binaries in a separate
Oh, you use the update checker in your build script, not in LMS...
The Update script 1) Updates itself from github 2) Grabs the update link the LMS saves via Update.pm. Then Downloads the noCPAN tarball 3) Downloads the other LMS customizations and init.d files from github 4) updates all of the permissions 5) Repacks the extension
But that update script is run on your end, not the user's? The latter would simply download the resulting tcz file?
If you were to build the tcz from the LMS build system. Some minor changes to the LMS customizations would be needed. The update script would get much smaller. At this point, the only file likely to ever change was the init.d script. Not sure how we could coordinate this.
I take it from the update script that you're running it on a Pi (eg. checking for OpenSSL)? I might give porting it to our build system a try when I find a few spare cycles.
-- Michael _______________________________________________ beta mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/beta
