-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi
While working on MidCOM here, we stumbled on a simple problem: Theoretically the namespace conventions of MidCOM bring you an worldwide, unique tree of elements that could be replicated without problems. In reality this brings a big administrative overhead: Each SnippetDir used globally has to have the same GUID. Pratically this is at least difficult to enforce that everyone works with the same structure. Not only we need to bring a standarized Top Level Snippet-Colletion with us (for .com,.net,.com,.org and for about 180 other TLDs of different Countries, not to mention the Sub-TLDs like .co.uk or .ac.uk...). While this could be done, the problem continues if you imagine a larger company, that uses multiple developement servers which should work in the same domain. I'm not sure what to do here. It seems to me that we'd need a customized Packaging system for MidCOM Packages which does not rely on repligard to move MidCOMS around. Multiple discussions seem interesting here: 1. Filebased Storage for distribution 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... What do you think? Live long and prosper! Torben Nehmer - -- Torben Nehmer, Munich, Germany http://www.nathan-syntronics.de, mailto:[EMAIL PROTECTED] PGP Public Key ID on wwwkeys.(de.)pgp.net: 0x7E9DE456 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: Weitere Infos: siehe http://www.gnupg.org iD8DBQE8tDiIJPh4Kn6d5FYRAnKJAKCq5RvMQ1UH2kSAKs297GS4eBSJsACfWoaD 38yABESIJwYOIOa44uSRjpY= =WhVj -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
