Karl, Sorry, my examples may not have been very clear. The reason I chose those was simply because they are the locations on CrossWire where zips can already be found.
Also, we use 'raw' in 2 different places, which also might have been confusing: /pub/sword/raw - raw module library installation /pub/sword/packages/raw - raw zip packages of single modules. We also have: /pub/sword/packages/win - windows installers for individual modules /pub/sword/packages/mac - .swd modules for mac Hope this clears things up. I agree: ../ above repo root is slightly evil DM's suggestion of a symlink to your cached directory is good. -Troy. Karl Kleinpaste <[EMAIL PROTECTED]> wrote: >"Troy A. Griffitts" <[EMAIL PROTECTED]> writes: >> We could do something similar where we check, e.g. <Repository >> Path>/../packages/raw/<Mod>.zip and use it if it exists. > >I am mildly uncomfortable with too much implicit navigation around a >repo tree. In mine, there is just a "zip" directory, sitting at the >same level as mods.d and modules. I don't see a lot of benefit to going >up and around a directory level, or why e.g. "raw" is to be preferred. > >All that said, I'm not seriously uptight about any of this. > >_______________________________________________ >sword-devel mailing list: sword-devel@crosswire.org >http://www.crosswire.org/mailman/listinfo/sword-devel >Instructions to unsubscribe/change your settings at above page > > _______________________________________________ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
