Quote:
Originally Posted by Adam B.
Well, here's a question, is it best to do a per-application install, or to install everything into a single directory eg: /usr/local/bin. Either way would technically work, and if you use ipkg, you could run an ipkg remove to delete it. But as you say, the average user isn't going to have access to the command line.
|
For applications that the user does not need to click on in the Content Lister, /usr/local/bin would be the usual way to go. Apps he has to click on to start, I proposed the /media/*/programs (symlinked from /usr/local/programs) for. However, whether to place the whole app there or just a manifest and starter script, mmmh, I'm not sure. Putting all in one directory allows the user to "uninstall" an app by deleting without leaving too many traces behind.
ipkg remove could be included in the GUI frontend. But that's a feature for version 2 or so...
---
PS: Just two examples of .ipkg contents:
(1) Standalone application (e.g. emelFM2, go, xtetris, ...)
/usr/local/programs/APP/manifest.xml
/usr/local/programs/APP/app.sh
/usr/local/programs/APP/app
/usr/local/programs/APP/app.so
depends: iliadx11
(2) Library package (e.g. patched X11 libs, GD, libxml)
/usr/local/lib/lib.so -> lib.2.so
/usr/local/lib/lib.2.so -> lib.2.0.3.so
/usr/local/lib/lib.2.0.3.so
/usr/local/etc/lib.conf
(3) "indirect" application (e.g. fbreader, open office)
/usr/local/lib/ipp.so
/usr/local/bin/ipp
/usr/local/etc/ipp.conf
/usr/local/var/fonts/helv.ttf
post-install script: add to content lister
pre-deinstall script: remove from content lister
Note: Type 3 depends on not-yet-existing feature of safely extendable content lister configuration.
(4) command line application (e.g. screenshot utility, Perl)
/usr/local/lib/cpp.so
/usr/local/bin/cpp
/usr/local/etc/cpp.conf
/usr/local/lib/perl/lib/*
Note: Type 4 applications are for power users.