On Thu, 2009-05-21 at 20:23 -0700, David Brownell wrote:
> On Thursday 21 May 2009, Zach Welch wrote:
> > I feel like this is a "dumb question" but here goes.... Why [are] all
> > of the TCL configuration files (src/target/{target,board,interface}/*)
> > located in src/target/ instead of src/tcl/?
>
> And why "src" instead of a toplevel "config"?
> Why named .../*.cfg instead of .../*.tcl?
Regarding the extension: It's Tradition. [[ *cue Broadway music* ]]
There are too many documents (and .cfg files themselves) to buck it.
OpenOCD has been around for a while, and this would seriously confuse
things for users reading docs (on external sites that we can't update).
Also, because they are not really TCL scripts. They are Jim TCL
scripts, so -- if anything -- they should be renamed '.jim'....
Myself, I would agree to 'svn mv src/tcl ${DST}', DST=tcl or DST=jim.
Other opinions? [[ *music swells* -- exeunt ]]
> Why don't you make a proposal for a revised
> structure. I'd plan for "target/*.cfg" and
> "board/*.cfg" to grow enough that they'll
> need another level; maybe targets should be
> grouped by vendor sooner, rather than later.
I was trying to punt this architectural work to Wookey, but I have
already posted a similar idea in my reply to Duane. Since he expressed
the initial interest with the configuration files (and I know he can
handle the technical challenge), I was hoping to delegate this work,
either to him or someone else qualified.... Say... you would do....
If someone does not take charge, I will commit the ideas to The List.
Ultimately, it will take a SVN committer to make these changes, but
someone else could probably write a script that will take the proper
actions for us....
Cheers,
Zach
_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
