smxi sgfxi svmi :: developers
set development options

See sticky options for standard user options. This section is just for advanced dev stuff.

Remember, always start with the latest bunch of script files from the script svns: smxi, sgfxi, svmi (and latest project, inxi). These can and do change rapidly at times, while at others the stuff is largely stagnant. Take a look at the source -> changes to get a feel for the current speed of development. Currently nobody has svn write access but me, the author, but if someone commits enough code, and it's done to the style of smxi/sgfxi, and it works, is a real improvement, is debugged, fits the logic, etc, that could change in the future.

Please do not use any of these options unless you have a good idea of what you're doing

These are useful for working on the script and setting various hardcoded values while you debug and hack etc.

One big advantage of using these is that you won't accidentally include these tests and flags in the working script itself.

smxi sticky options

Sometimes you might want to always use an smxi option, or change some other value in smxi. Now you can do this easily, by simply adding an smxi option file, like so:

# create the file first, as root in terminal
touch /usr/local/bin/smxi-values

You can also change any default paths or file names if you want to do something like for example run a dev version live off your own web server, and so on.

Since these scripts do not use any hard coded paths or values in general, and everything is set in the top globals, you can quite easily modify anything you want in terms of locations, file names, etc.

top

sgfxi sticky options

sgfxi is a lot harder to work on than smxi because it has to handle such constantly changing circumstances. Let's face it, non free drivers on free systems just suck. But we have to live with it for now.

I've built in a series of advanced options to help test and debug certain components. Please do not use any of these options unless you have a good idea of what you're doing

These are useful for working on the script and setting various hardcoded values while you debug and hack etc.

One big advantage of using these is that you won't accidentally include these tests and flags in the working script itself.

First, make sure you have the file:

touch /usr/local/bin/sgfxi-values

And here are the normal dev options for you to use:

top

svmi sticky options

svmi has a very limited set of useful dev options, but here's the ones you might find of use utility.

First, make sure you have the file:

touch /usr/local/bin/svmi-values

And that's about it for the standard dev type options for these scripts.

top

More advanced methods and tricks

While I'm sure people will at some point come up with weird uses for these source files, some things that pop in my head as possible options is to change the script home, change the script source url, and so on.

For sgfxi testing, please also first read set test data, which explains how to use the built in testing and debugging options in sgfxi.

# note: no / after last directory
SCRIPT_HOME='/home/fred/devdir'
SCRIPT_NAME='temp-name'

# note: / after last dir for download urls
# for smxi/svmi/sgfxi values files
SCRIPT_DOWNLOAD='http://localhost/distro/'

I'm not suggesting or recommending this type of tweaking, but it is something you can do for various tests, running your own patches, or whatever. Play around with it, I don't care, as long as you can handle the messes you might make, do whatever you want.

top