Joined: Oct. 2003
||Posted: Aug. 15 2005,01:50
Nice to see some interest in extension building..
I'll assist where I can..
|The documentation (in the web site) is still not clear. For instance, there are sections on creating uci and tar.gz but none on dsl. Further, the section on uci only talks about modifying an existing uci.|
Documentation is currently being revamped. More to come. Stay Tuned.
|1. Optimal memory use (uci > tag.gx > dsl)|
2. Sections of the file system affected: (opt < opt... < all)
Both of these topics are heavily discussed in the forum threads..
Search using keywords .uci .tar.gz .dsl
Much detail into your items in #3 is also listed and discussed.
There is also a .pdf how-to for building extensions in the repository
for the budding extension builder.
Feel free to submit an addition to this which covers more details
about the inner workings, pros&cons, and structure of extension types
for more advanced extension builders.
|For instance: I compiled cvs to allow pulling code from sourceforge. As far as I can tell, the only convenient way to package it is as a .dsl so it can be placed in /usr/bin. (Parenthetically, adding /opt/bin to the default path would ease this problem.) |
Yes, an /opt/bin would work for single binaries.
But more complicated extensions would require that idea to be
expanded to /opt/usr/bin, /opt/usr/lib, /opt/usr/share etc...
The wrapper is an easy way to be precise about the path your application needs.
|export PATH=/opt/foobar/usr/share:$PATH |
allowing you to keep the original pathing structure intact under /opt ,
just like it would be normally in the root file system ..
Please feel free to contribute, submit, or discuss any part of
extension building with the DSL userbase, as extensions are always
improving and changing to meet the goals of lower ram usage,
ease of installing/removing (package mgmt.) and adding more
functionality normally found in distros 10-20 times the size of DSL.