Quote:
|
Originally Posted by Adam B.
The problem is that you cannot simply select an ipkg file from the contentlister. A change would have to be made to the er_registry.txt in order to allow for this. The iLiad only allows running of scripts, so a script to kick off the process will be necessary.
|
I know. Because of that I wrote in my first post, that we need to add a small "warpper" srcript at the moment. That script would just call ipkg. Later, when iRex provides a way to safely add extensions to the content lister, that script sould no longer neccessary.
Quote:
|
Originally Posted by Adam B.
Edit: Besides, I don't think that we should allow all ipkg files to be run anyway. I can see a user assuming all all ipkg files will work, install something that wasn't made for the iLiad, and fill up their root file system. If we force an iLiad specific script to install it, it will prevent such things from happening.
|
Good point. However, I'd prefer to simply use another extension, maybe ".iliad". ipkg shouldn't be picky about that...
And BTW, someone could write a graphical ipkg frontend. With scripts that would be rather hard to do in a reliable way. I could imagine that iRex would be willing to add that frontend to the standard installation if it was well written and included a big enough warning message.
Underscore works? Good, I'd prefer that to the dot, too.