Idea for making RiscPkg more flexible and user friendly
I was tossing this idea around, and it was suggested that I post it
here, so here goes. This might not work in all situations, either, but
for an application where there's just one app that goes into a
directory (read: most apps,) and nothing else, this would work.
Rather than have the package contain a hierarchy of directories, and
the application to be installed being in one of those directories...
have the application be the only directory at the root level of the
package ZIP file, with the RiscPkg info inside the application.
Then, the user can copy the application to the drive, in whatever
location, and run it. Upon first run, the application would invoke the
package manager, to download any necessary dependencies, and register
the app in the package database.
This could even handle moving the app, by comparing the directory it
was originally installed in, with the <Obey$Dir> on run, and if
different, notifying the package manager of the change. Deletion would
be more difficult, but probably possible to detect. Worst case, on
every package manager operation, you scan for changes.
This could also be implemented in downloading apps from a repository -
just drag from the list of apps in the repository right to the
directory you want to install in.
Just a thought...