iLiad iLiad 3rd Party programs standardization

[tororebelde]

Originally Posted by mtas

Last edited by Alexander Turcic : Today at 02:21 PM. Reason: attachments temporarily removed, see next post --alex

Doh, now I realize! I only was able to download the first attachment while Alexander moved them

[Alexander Turcic]

Originally Posted by Adam B.

The first 2 were okay, it was only the third that would fill the root filesystem if the other was not run first.

OK, I added them back except for emelfm2_install.zip.

[mtas]

Originally Posted by Adam B.

The first 2 were okay, it was only the third that would fill the root filesystem if the other was not run first.

This was my faulty instructions (I should not really try to write them running a fever. . . )

I didn't stress that the create_local script should be run first. It's now part of the ipkg package as a preinstall script.

Regarding my use of the directory name local instead of _local this was a deliberate choice, it makes it a bit easier to check that the wanted files have been created. In the future I will use the name _local instead.

The version of emelfm2_install.sh enclosed here includes the preinstall that creates the necessary symlink.

[Alexander Turcic]

Originally Posted by mtas

This was my faulty instructions (I should not really try to write them running a fever. . . )

No problem, I just wanted to make sure that we don't have any unhappy faces today - this is why I removed the file.

Hope you'll get better fast!

[Alexander Turcic]

Any progress on the standardization?

Now that iRex released firmware 2.9.5, it should be very soon possible to use a recovery software in case one bricks his device. Meaning more people willing to participate in running 3rd party software

[vranghel]

Originally Posted by Alexander Turcic

Any progress on the standardization?

Now that iRex released firmware 2.9.5, it should be very soon possible to use a recovery software in case one bricks his device. Meaning more people willing to participate in running 3rd party software

Whoo! Im sure that the unbricking utility will bring LOTS of programmers out of lurk mode. Many great things to come!

[TadW]

Originally Posted by vranghel

Whoo! Im sure that the unbricking utility will bring LOTS of programmers out of lurk mode. Many great things to come!

I agree! After some startup hickups, iRex is finally listening to their customers and working hard to make our lives better

[Adam B.]

I agree, we need to make a decision... A poll maybe? There seems to be a lot of good ideas, and nobody is really disagreeing on them.

I like Henry's idea of /usr/local and ipkg.

We should have a preinstall script check for and create the following.

/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/share -> /media/*/_local/share
/usr/local/include -> /media/*/_local/include
/usr/local/programs -> /media/*/Programs

After the program is installed /usr/local/programs should contain a folder with a launcher script, manifest, and icon.

For removing an application, we can create a simple script that will execute ipkg remove applicationame. We can put this script along with a manifest and icon in /usr/local/programs/Uninstall. From there, the user can simply navigate to that folder if they want to uninstall an appliation. They can select it, have a confirmation box pop up that says "Are you sure you want to remove $program?" that they will have to select, and the ipkg command will run.

Does anyone have any problems or disagreements with this? I think it solves almost every issue we would run into. The only problem I see is if a user swaps around memory cards of the same type.... but in that case, they should know that they have to reinstall all the applications.

Also, I agree that we should rename ipkg files to .iliad. This will avoid confusion and allow us to eventually put an entry in er_registry.txt.

[Alexander Turcic]

I agree a poll (in a new post on the frontpage) is probably a good idea to give every dev a last chance to think it over.

[Adam B.]

I'll set it up.

[nekokami]

I'm not getting something. All ipkg packages need to be matched to the OS in order to install, right? Why do we need to change the name to .iliad? Is there anything else in the package that can be used to identify the platform the package was compiled for?

I'm just generally wary of changing a standard file extension, I guess. But if there's a real need for it, then I wouldn't argue against it.

[Adam B.]

AFAIK, they don't need to be matched to the OS, just the processor I believe. I'm afraid that once we start allowing users to download ipkg's that weren't made for the iLiad, that they could replace important files or fill up the file system. Changing the extension would prevent that.

[Adam B.]

I've been playing a bit more with ipkg, and it already has the option to create and delete symbolic links from root to the memory card... We should be able to use internal tools and create simple ipkg packages.

Add into /etc/ipkg.conf

dest cf /mnt/cf/_installed

To install:

root@ereader# ipkg -d cf install xournal_0.3.3-iliad.0.1_arm.ipk

Then:

root@ereader# ipkg-link add xournal
*** Command: add
*** Locating package
*** Found package on /mnt/cf/_installed
*** Adding xournal
*** Done.

root@ereader:/usr/local/bin# ls -la
drwxr-xr-x    2 root     root         1024 May  9 05:35 .
drwxrwxr-x    5 root     1000         1024 May  9 05:35 ..
lrwxrwxrwx    1 root     root           40 May  9 05:35 xournal -> /mnt/cf/_installed/usr/local/bin/xournal

# ipkg-link
Usage: 
    /usr/bin/ipkg-link add    packagename (links "packagename" to root filesystem)
    /usr/bin/ipkg-link remove packagename (unlinks "packagename" from root filesystem)
    /usr/bin/ipkg-link list   mountpoint  (lists packages on "mountpoint", e.g. '/mnt/card')
    /usr/bin/ipkg-link mount  mountpoint  (links all packages on "mountpoint", e.g. '/mnt/card')
    /usr/bin/ipkg-link umount mountpoint  (unlinks all packages on "mountpoint", e.g. '/mnt/card')

[narve]

Originally Posted by Adam B.

dest cf /mnt/cf/_installed

I guess we can then use

dest userrepo /mnt/cf/_installed

instead, so that MMC users can use

dest userrepo /mnt/card/_installed

Then all commands will be similar for both CF and MMC card users:

root@ereader# ipkg -d userrepo install xournal_0.3.3-iliad.0.1_arm.ipk