Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 13 Apr 2004 23:32:05 +0400
From:      Sergey Matveychuk <sem@ciam.ru>
To:        Garance A Drosihn <drosih@rpi.edu>
Cc:        freebsd-ports@FreeBSD.org
Subject:   Re: Second "RFC" on pkg-data idea for ports
Message-ID:  <407C4035.8020609@ciam.ru>
In-Reply-To: <p0602041abca1e49dde40@[128.113.24.47]>
References:  <p0602040cbca10a7dbe52@[128.113.24.47]> <20040413121925.GB29867@voodoo.oberon.net> <p0602041abca1e49dde40@[128.113.24.47]>

next in thread | previous in thread | raw e-mail | index | archive | help
Garance A Drosihn wrote:

> But as I thought about adding future features, I ended up with
> something that looks more and more like XML...

I really don't understand why you want to use XML-like format?
I think it may be XML (because of we have a standard) or complete non-XML.

 From your WEB-page:
-------------------
The "<data-format>" tag is expected to identify the version of the 
format used for this individual pkg-data file. As time goes on, we will 
probably want to expand this format in some manner, and this allows us 
to have multiple formats of pkg-data files in the same ports tree. If 
someone has a better name than "data-format", I will be happy to use it. 
I also wonder if it might be better to collapse the data-format value 
into the initial "freebsd-ports" tag. Ie, the pkg-data information would 
start with a tag-line of
==<freebsd-ports:v1>
but still end with a "</freebsd-ports>" tag.
-------------------

In XML we can get something like: <freebsd-ports version="1">.
For parsing we have ready parsers.

Or, if we wish to avoid complexity, we can use non-XML.
E.g.
=== freebsd-ports
...
=== !freebsd-ports

Why to mix them?

-- 
Sem.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?407C4035.8020609>