Just got up to speed with the long thread about Midgard Components,
great stuff!
I think our repligard system is a great concept, but also poses a lot of
problems. It mandates that all content be in the database if you want to
have a one-go replication process set up. As a result we kind of fork
away from the open source community, because the tools produced by the
community don't work for us in a comfortable way. vi, emacs, cvs, rpm,
apt-get, they are all of no use to us. (Well, not easily, that is)
The discussions in this thread made be combine thoughts and come up with
a 'serialize and bootstrap' concept, one that absolutely needs refining,
but potentially could be of great support to the MidCom initiative.
CONCEPT
namespaces within the snippetdir/snippet hierarchy will be tagged as
filespace snippets. a utility 'bootstrap', can scan the configured
filesystem directories for files, wich will be imported as snippets, a
utility 'serialize' will flatten out existing snippet trees for writing
to the filesystem.
FORMAT
The format of the 'serialized' snippets must be of a workable design, so
that normal tools will work on it. So instead of using XML, we might
turn a snippet into a directory whith files for each of elements:
snippetdir/snippetname/GUID
/SG
/code
/author
/.... (etc)
a snippetdir should also hold files to discribe it properties.
If properly designed, this would allow us to use the timestamps and the
GUID to interface with repligard to do the bootstrapping/serializing.
This would enable us to use existing packaging tools to distribute
aplications, use cvs in shared development, etc, while still having
repligard at the core.
wkr,
--
Envida http://www.envida.net/
Armand A. Verstappen Graadt van Roggenweg 328
[EMAIL PROTECTED] 3531 AH Utrecht
tel: +31 (0)30 298 2255 Postbus 19127
fax: +31 (0)30 298 2111 3501 DC Utrecht
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
