roberts
Group: Members
Posts: 4983
Joined: Oct. 2003 |
 |
Posted: June 24 2004,00:22 |
 |
The hardest part of creating a ci has nothing to do with compressing them. The hardest part is to make a self-contained application under /opt. Because openoffice and firefox are pretty much self contained and are under /opt they were good test cases. I have since made python2.3.4 which works under /opt so to make it a ci is easy. Also, the ci has a limitiation of being read only. That is why there is an oouser.tar.gz. Those parts that require updates can be "linked" into a writeable directory. I see user Chris V made a firefox user file. Try to avoid making .dsl as they cause additional demands on the system. Sometimes, you will be required to make a shell wrapper to start the app. As being self contained implies that the app's libraries are also stored locally with the app. This usually implies requiring a LD_LIBRARY_PATH, thus the shell wrapper. Anyway, make the app. Test it as a .tar.gz. Once the app is working then to make a ci do the following.
1. The app is installed into /opt in the your_app directory
1. become root
2. cd /opt
3. mkisofs -R -hide-rr your_app | create_compressed_fs - 65536 > /mnt/somedrive/your_app.ci
Note: there is currently a limit of 4 cloop devices available. So, I don't see a need for mnay .ci files unless the app is very large and is very popular.
|
.
DSL Market ,
Great VPS hosting provided by Tektonic
