[Swift-devel] Proposed sites.xml management for 0.92 release

[Sarah Kenny]

On Mon, Feb 14, 2011 at 10:25 AM, Michael Wilde <wilde at mcs.anl.gov> wrote:

> Sarah, David,
>
> Yes, I think gathering the site templates is indeed the first step. Then
> parameterizing them, including provisions for removing lines (per the
> GetSites spec page).
>
> And I agree that we should set swiftrun aside (and later bundle any needed
> parts of it into the swift command).
>
> David, I reviewed the current swiftconfg, and I feel it can be greatly
> simplified by rewriting as a shell script.
>

oh, if we're going to actually do a re-write rather than leverage the code
david already wrote my preference would be for python over shell...david do
you know python? if not then shell is *ok* with me, it'll just be a little
slower and clumsier for me :P i thought if we were sticking with the perl i
would not help write it but just write the doc, but if we're doing a
re-write i'm guessing it will take the effort of both of is (?)


>
> There is some reasonable shell arg parsing logic we can lift from:
>
>
> https://svn.ci.uchicago.edu/svn/vdl2/SwiftApps/SwiftR/Swift/exec/start-swift
>
> (arg parsing is right after the usage() function around midway through the
> script)
>
> - Mike
>
>
> ----- Original Message -----
>
>
> sounds good to me david...i don't know perl so maybe my time would be
> better spent using it and updating the doc in sync with you working on the
> code (?) i think first we want to separate swiftconfig from swiftrun...it
> would be good if users who are already used to running regular 'swift' to be
> able to transition to using swiftconfig (i realize this probably affects the
> doc more than your code, i just wanted to mention it).
>
> so, maybe the first step is switching out the sites templates?
>
>
> On Fri, Feb 11, 2011 at 8:51 PM, David Kelly < dk0966 at cs.ship.edu > wrote:
>
>
> Would it be easier to modify the existing swiftconfig to adjust to the new
> format of templates?
>
>
> The main steps that were outlined are nearly already completed with
> swiftconfig
>
>
> - The commands are already there
> - A set of templates already exists, but would most likely be replaced with
> the ones verified by automated testing in the format Justin specified
> - A good start for documentation using swiftconfig on a variety of
> configurations is at
> http://www.ci.uchicago.edu/wiki/bin/view/SWFT/LearningSwift
> - Documentation for commands and syntax is there, swiftconfig -h and
> swiftrun -h
> - List all templates with swiftconfig -list templates (already knows the
> correct order of where to look for templates)
> - Help for specific templates is a good idea. That would be pretty
> straightforward to add
> - Support for applications and application groups is already there
>
>
> If we started over it seems like we would be duplicating a lot of code
>
>
>
> --
> Michael Wilde
> Computation Institute, University of Chicago
> Mathematics and Computer Science Division
> Argonne National Laboratory
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/swift-devel/attachments/20110214/0ab2a25b/attachment.html>