On Fri, 12 Nov 2004, Russell Gold <[EMAIL PROTECTED]> wrote: > A bit earlier in the thread, I tried to summarize them:
I've seen that, but then Steve responded with a list of things you didn't know about yet. Let me take a few steps back and first look at the functionality only. We have: * a local directory holding libraries. (both) * remote site that may hold libraries not yet installed on our system and a mechanism to get the files from the remote site to our system. (both) * information about a specific layout of directories and files both locally and remotely - that's what I understand the term repository to mean in this context. (both, but optional with getlibraries and central part of the logic in dependencies). * can create filesets or path from the libaries in the local file system. (both, but optional with getlibraries and central part of the logic in dependencies). * dependencies relies on a single local cache, getlibraries expects all builds that want to share the cache to collaborate. * dependencies relies on filenames, getlibraries uses timestamps in addition (or maybe other mechanisms) to determine whether something already is in the local cache. Am I missing a crucial piece of functionality for either of both? Am I misrepresenting anything? Stefan --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
