Bugs for Sorcery are reported here

[bugzilla-daemon AT bugs.sourcemage.org]

http://bugs.sourcemage.org/show_bug.cgi?id=6981





------- Additional Comments From acedit AT armory.com  2005-01-03 17:09 -------
We all have our days, i certainly have mine where im not the most friendly 
person :)

'&' is definitly not a good seperator since it means something to bash. Why 
dont
we work backwards from tla...and reduce the complexity of the url...I think
you're doing more work than you need here :)


The first step is to register an archive with tla register archive, then we
either tla update or tla get, then bundle it all into a tarball again.

Theres really only three pieces of information we are worried about from the
url, the location of the archive (which could be anything tla can parse, and
could be a url of its own, with a http:// and all), the archive name itself, 
and
finally the branch-spec (that category--branch--version[--patch-level] thing,
which of course arch is free to interprit as it wants).

Most things dont use % as a seperator, so thats probably as good a thing as 
any,
maybe ! would work also, or something clever like :: as a two character
seperator. I'll use % for now. The thing to be careful of is that the fields 
in
the url arent going to be using the seperator, so '@' would obviously be a bad
choice since archive names always have an @ in them, same for '--' for obvious
reasons.

Anyways, rolling the three pieces together with % we get this:

tla://location%archive%branch-spec

The handler just has to seperate through the % fields and then make the 
required
tla calls. Turning the above stuff into psuedo code:

Strip the tla:// off the front and call cut or sed three times

tla register-archive $TLA_ARCHIVE $TLA_LOCATION (or fail)
If theres a tarball; then
  unpack it
  tla update $TLA_BRANCH_SPEC $S_FILE
else
  tla get $TLA_BRANCH_SPEC $S_FILE
fi (or fail)

tla register-archive -d $TLA_ARCHIVE

(re)create tarball from $S_FILE



-- 
Configure bugmail: http://bugs.sourcemage.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.