Quote:
|
Originally Posted by mtas
The second one: create_local.zip will create the necessary directory structure needed in the root of the file system it is run from. I.e. if you place it somewhere on a CF card it will create needed directories/files on the top level of that card. It will also create a symlink from /usr/local to the directory local that the script has created. For a CF card the structure created will look like this:
/usr/local -> /media/cf/local
/media/cf/local
/media/cf/local/additional_progs (this is where start-up scripts should go)
/media/cf/local/home (contains the file environment that contains common environment variables)
The last file, emelfm2_install.zip contains a single shell script which has an ipkg file embedded. When run the ipkg file will be extracted and installed. A post-install script is used to set up the start-up script for the application in /usr/local/additional_progs.
Have fun  |
I like your idea for the first script. I would, however, change it to /media/cf/_local so the local directory is hidden from the content lister.
Also, did you use that script in the preinstall for the emelfm2_install.sh ipkg? If you did, it did not run, or ran incorrectly. This should be a standard practice so users do not have problems with their filesystem.