The core Naviserver repository on Bitbucket includes several important modules like nslog, nssock, etc., which are placed in this directory structure:
foo/naviserver/nslog/ foo/naviserver/nssock/ A whole bunch of add-on modules (nsoracle, nsssl, nszlib, etc.) are each in their own Mercurial repositories on Bibucket. (I'm not sure why; it'd seem simpler to me to have all the modules in the same repository as the core server, but whatever.) So in theory I can put the local working copy of each module anywhere in my directory tree I want. But what is the recommended convention? Should they be placed like this: foo/naviserver/nsoracle/ foo/naviserver/nsssl/ Or like this: foo/nsoracle/ foo/nsssl/ Btw, with the modules I've looked at so far it seems like either location should work, but I'm not sure if that's intentional (and a feature that must be preserved) or an accident. The Naviserver build scripts are setup to REQUIRE installing the core Naviserver first, before building add-on modules. Building the add-on modules then uses the installed core headers and libraries rather than from their original source checkout. (In my own work I've preferred to do the opposite, build the core and modules together using the same source tree and only install them once together at the end, but I assume you folks have a good reason for preferring their method.) -- Andrew Piskorski <a...@piskorski.com> ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk _______________________________________________ naviserver-devel mailing list naviserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/naviserver-devel
