Quote:
|
Originally Posted by Adam B.
I heard someone say that /opt is already in use on the iLiad, how about /var/opt? From there we can implement something similar to what Henry mentioned, but instead link it to /media/???/_opt. In there, we can have share, bin, lib, etc.
Using ipkg isn't a bad idea.
|
Yes, /opt is taken. But /usr/local is available. We should stick to some standard directory, I'd think...
Also, ipkg is already available on the iLiad, no need to put it on.
When reading the responses, I see a clear pattern:
(1) People tend to forget that the installation must be doable for everyone. This basically limits us to Drag&Drop on the PC side and Click-in-the-Content-Lister on the iLiad side.
(2) Putting one or more symlinks onto the root directory seems to be consent. However, as vfat does not support symlinks (I forgot...), we'd better go with multiple symlinks, as this allows advanced users (that can use the command line) more flexibility. What about
:
/usr/local (real directory)
/usr/local/lib -> /media/*/_local/lib
/usr/local/bin -> /media/*/_local/bin
/usr/local/etc -> /media/*/_local/etc
/usr/local/var -> /media/*/_local/var
/usr/local/programs -> /media/*/programs
Could someone check if "_local" or ".local" are hidden from the content lister? If both are not, we maybe should use "/media/*/programs/internalfiles" instead to prevent cluttering the card's root directory.
(3) People seem to prefer scripts over ipgk. That apears strange to me. Most of the things, these scripts should do are already part of ipkg, in fact, it was created to do this. It should take care of duplicate libs, allow uninstallation (even if there are libs used by 2 or more programs), check disk space, etc. Google turned up this site:
http://www.linkstationwiki.net/index...or_developers) Have a look.