tags

[Jan Hudec]

On Sat, Feb 11, 2006 at 14:22:55 -0500, Aaron Bentley wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Jan Hudec wrote:
> | Ás for the format, rio (mentioned on wiki) is not appropriate for other
> | reasons. Basically to best utilize existing merge code, each property
> must be
> | recorded on a single line -- but rio escapes \n -> \n\t.
> 
> I am starting to think that an explicitly versioned scalar file format
> would be useful.
> 
> e.g. each value in an inventory entry would be versioned separately,
> making scalar weave merging of inventory entries exceedingly simple.

It would mean tons of files, which I has it's problems. Given that the
properties are usually short and most of them don't allow newline char in the
value anyway. In fact I can't think of any that does:
 - Ignores: Globs interpret escapes, so they can require \n to be used.
 - Executable flag: The inventory id is or isn't there.
 - Filters: Names of filters are fixed
   (Filters are common property for line-endings conversion, charset
   conversion, keyword expansion and possibly other conversion that may be
   desired)
 - Subtree urls: URL never contain whitespace, let alone newlines.
 - Tags: I don't think allowing newlines in tag names will help anything and
   revision IDs don't contain them.

So there is just one thing that may want newlines -- revision annotations.
So they will need specific solution.

Another thing is, that properties should be in for 0.8, which is mere 3 or
4 weeks away. It's not enough time to invent new file format. Certainly not
with the amount of free time I have.

-- 
						 Jan 'Bulb' Hudec <bulb at ucw.cz>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20060211/88ea9c3c/attachment.pgp