mikshaw
Group: Members
Posts: 4856
Joined: July 2004 |
 |
Posted: Oct. 14 2006,14:08 |
 |
I recently downloaded a small pile of non-pixmap gtk1 themes that work in DSL, and I'm looking for some feedback on what the most useful method of packaging would be. They will be packaged as gtk1-themename.tar.gz and install into /home/dsl/.themes so they can be automatically found by switch.dsl and be edited by the user.
The fact that they'll install into ramdisk (and the fact that I tend to want no more files than necessary installed at any given time) makes me want to package them individually.
The thing I haven't decided on yet is how to handle the engines. Some themes require particular theme engines. Having the engine included with every theme that requires it is wasteful, so there are a few options on my mind:
Option 1: Include the engine with the theme that was originally released with the engine. This will require each additional theme that needs an engine to have its module_path point to the original theme's directory. This is the method I'm currently using on my system. It's quite portable, and is pretty close to the way the original theme packages are set up. The module_path for each engine-dependent theme also includes /usr/lib/gtk/themes/engines so the theme can be used if you already have switch.dsl installed (and if the required engine is actually included in switch.dsl).
Option 2: Release the engines as a separate package or packages, installed into /home/dsl/.themes or as a uci. Each engine-dependent theme will have the same module_path regardless of what engine it uses. If the engines are released as a uci, it will need to remain mounted for as long as gtk apps are being used. This method was the first thing I tried, but personally I think it's a little messy.
Option 3: Release theme packs, with each pack including all themes that require a particular engine. This method is my least favorite, although I know many people like packs.
Option 4: Release everything as one package. This would be convenient as a uci, but as I said before it would need to remain mounted permanently and I tend to prefer not installing things I have no plan to use. This also means the themes are read-only.
Option 5: Release both a theme pack and individual themes. This would be a combo of two of the above options.
Any feedback on the pros/cons of these options, additional options, or any other ideas are welcome.
Thanks for reading.
--------------
http://www.tldp.org/LDP/intro-linux/html/index.html
|
.
DSL Market ,
Great VPS hosting provided by Tektonic
