Digidude, this one's for you!
You said elsewhere "[...] until i can work out exactly how the blue button downloads are done."
The trick is to create your own package repository.
You already host the packages, for example the HD skins.
To have a package repository, you need a list of packages, and to tell ipkg where to find your repository (bake this into the image).
The package list is a file name "Packages.gz" which should be publicly available and should contain information on the packages you host.
I've just built a repo for the alu skin and for "lsof", by placing the ipk files into a folder on my web server, and writing this simple Packages file (which I later gzipped).
The names are carefully crafted. You must use this format: "enigma2-plugin-<directory>-<package.name>"
The alu skin will show up as "brushed.alu.hd" in the downloads under "skins", while "lsof" will appear under "tools" (new section).
So, on my server, I've created a new directory, called it tm800 (it can be anything), and placed in it the two ipk files and the Packages file with the contents listed above. Then I gzipped the Packages file, so it now looks like this:
The /var/www directory is the root of my apache web server, so the file list and the packages are accessible as "http://server/tm800/Packages.gz", etc.
Now on the box itself, create a new file under /etc/ipkg, for example joypad.conf, with this line inside:
Needless to say, my server is only available from inside the house, I reference it without a domain.
Yours should be public, so, you can do what UR did, create a public URL that can be accessed from TM800s everywhere.
See http://en2.ath.cx/un2/Packages.gz (check out /etc/ipkg/ur-feed.conf).
Run "ipkg update" after you make changes to the Packages.gz file on your server. This command downloads the list to the box and unpacks the package information. It is this package information that gets used to display the list of downloadable packages in the Plugins panel. The Package names must match the format described above. The description is used in the menu (under package name, in the list). The file size and MD5 are used to validate the downloads (generate MD5 for your ipks by running "md5sum filename"). Arch should always be mipsel and maintainer should be you.
I hope this will help you organize your stuff into a package repository, which can easily be added to your image, and then all your users will simply click the blue button to download the goodies.
You said elsewhere "[...] until i can work out exactly how the blue button downloads are done."
The trick is to create your own package repository.
You already host the packages, for example the HD skins.
To have a package repository, you need a list of packages, and to tell ipkg where to find your repository (bake this into the image).
The package list is a file name "Packages.gz" which should be publicly available and should contain information on the packages you host.
I've just built a repo for the alu skin and for "lsof", by placing the ipk files into a folder on my web server, and writing this simple Packages file (which I later gzipped).
Code:
You don't have permission to view the code content. Log in or register now.
The names are carefully crafted. You must use this format: "enigma2-plugin-<directory>-<package.name>"
The alu skin will show up as "brushed.alu.hd" in the downloads under "skins", while "lsof" will appear under "tools" (new section).
So, on my server, I've created a new directory, called it tm800 (it can be anything), and placed in it the two ipk files and the Packages file with the contents listed above. Then I gzipped the Packages file, so it now looks like this:
Code:
You don't have permission to view the code content. Log in or register now.
The /var/www directory is the root of my apache web server, so the file list and the packages are accessible as "http://server/tm800/Packages.gz", etc.
Now on the box itself, create a new file under /etc/ipkg, for example joypad.conf, with this line inside:
Code:
You don't have permission to view the code content. Log in or register now.
Needless to say, my server is only available from inside the house, I reference it without a domain.
Yours should be public, so, you can do what UR did, create a public URL that can be accessed from TM800s everywhere.
See http://en2.ath.cx/un2/Packages.gz (check out /etc/ipkg/ur-feed.conf).
Run "ipkg update" after you make changes to the Packages.gz file on your server. This command downloads the list to the box and unpacks the package information. It is this package information that gets used to display the list of downloadable packages in the Plugins panel. The Package names must match the format described above. The description is used in the menu (under package name, in the list). The file size and MD5 are used to validate the downloads (generate MD5 for your ipks by running "md5sum filename"). Arch should always be mipsel and maintainer should be you.
I hope this will help you organize your stuff into a package repository, which can easily be added to your image, and then all your users will simply click the blue button to download the goodies.
Last edited: