View Single Post
Old 04-19-2007, 06:46 AM   #14
Adam B.
Addicted to Porting
Adam B. is a jewel in the roughAdam B. is a jewel in the roughAdam B. is a jewel in the roughAdam B. is a jewel in the roughAdam B. is a jewel in the roughAdam B. is a jewel in the roughAdam B. is a jewel in the roughAdam B. is a jewel in the roughAdam B. is a jewel in the roughAdam B. is a jewel in the roughAdam B. is a jewel in the rough
 
Adam B.'s Avatar
 
Posts: 1,697
Karma: 7194
Join Date: Oct 2006
Location: Indianapolis, IN
Device: iRex iLiad, Nokia 770, Samsung i760
Quote:
Originally Posted by tororebelde
This is good to me, but the fourth point I'm not sure how to deal with it. It has been discussed to use a common /opt/lib directory, and is the better for me, but since this will fast decrease free internal memory, a _libs on cards looks good for me. But don't understand your solution to avoid duplicated libs. Maybe I'm lost on translation?
The actual libs won't be stored on the internal memory, but linked to whatever memory card you use.


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. We wouldn't even need to make any changes to the contentlister to run it (thus preventing problems with a user running too large of an ipkg file). We can distribute the ipkg along with an installation script. It'll create the necessary directories and symlinks, remove the installation file, and change itself from an installer to the program launcher. Should be simple to do and easy for the user to understand.

I don't think that zipping the needed ipkg, script, manifest, and icon would cause much of an issue. XP has zip functionality built in. A user can easily open a zip as a folder and drag and drop into the memory card. Either that, or go through xp horrible zip wizard...
Adam B. is offline   Reply With Quote