On 10.04.02 (20:47), Torben Nehmer wrote:
> >> 2. APT Like packaging, working entierely without repligard
> >> 3. Using repligard with an wrapper script that can correctly
> >> handle MidCOM Elements by name, and not by GUID.
> >>
> >> Personally I'd prefer (2), because it will give the most
> >> flexibility...
> >
> > I'd vote for (3), because it's the easiest way to go. We could
> > let repligard handle the XML writing & parsing stuff as well as
> > building the right trees, deciding what to import/export etc.
> > and could adjust GUIDs accordingly to the respective target
> > database. If I'm not overlooking anything right now, we could
> > even implement MidCOM replication via (3) with YAMP, couldn't
> > we? (Using a script hook to replace MidCOM "domain" GUIDs.)
>
> Not neccesserily. You need a logic which can decide whether
> the SnippetDir in Question is already there or not. The
> problem is, that you cannot generalize the problem down to a
> Shell/Perl Scripting Layer, you need Information from the
> Midgard System for this.
Okay, then YAMP would not be a good idea. How about a
Midgard/PHP interface on top of repligard? Would still save a
lot of basic work ...
> Exactly that conclusion lead me to the point to propose
> implementing the packaging system in PHP on top of Midgard
> Core. It should that difficult to generate Package of a
> specific Component with PHP. This would also be easier to use
> for beginners, which often have problems understanding
> Repligard.
I think we have to be careful not to underestimate the amount of
work necessary to get a real packaging and replication
infrastructure to work -- Alexander already did it, so I think
it's easier to use repligard as a basis for MidCOM packager
tools.
phr
--
Linksystem Muenchen GmbH [EMAIL PROTECTED]
Schloerstrasse 10 http://www.link-m.de
80634 Muenchen Tel. 089 / 890 518-0
We make the Net work. Fax 089 / 890 518-77
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
