John, et al, After digging through the documentation a little more, what I see is that lcdproc is distributed as debian packages, which should make integrating with EMC fairly easy. Further, the interface is via a standard tcp socket. Thus no language specific interface is required, although a common interface module could be written to standardize the interface between lcdproc and EMC.
Thus from the perspective of EMC, it could include just the binary package, or create a sub-branch which includes all of the lcdproc source code too. Unlike classic ladder, it appears that no modifications to lcdproc would be required to use it with EMC. Which means the latest binaries should always be compatible, unless of course an upgrade was made which broke backwards compatibility. What would be the recommended approach, from the perspective of the EMC source code? Obviously the binary install would include just the binaries. But should the lcdproc source code be included with the EMC source code, or should that always run from the binaries, and just reference lcdproc as a separate open source project? Regards, Eric > (This is me speaking as in individual developer who happens > to be on the board, not speaking for the board as a whole.) > > I really don't want any developers to feel that they need > "board approval" > to make additions to EMC. Yes, it is important that things > be discussed on the developers list, especially things that > will add significant new dependencies to EMC. But nobody > should be discouraged from contributing code. > > It this specific case, as with classicladder, only a subset > of users are going to use the new functionality. As long as > the build system can skip building the new additions when > their dependencies are unavailable, I see absolutely no > reason why you shouldn't go ahead. Just make sure that > configure tests for the dependencies, and if they aren't > present, it prints something like "Warning: foo missing, bar > will not be built", instead of aborting the entire build. > > If there are runtime dependencies, then things get uglier. > If we list those as dependencies for the EMC2 packages we > force every user to install those packages even though only a > few want the functionality they supply. It's even worse if > the dependency isn't available as a package for Ubuntu - we > cannot and will not require the average user to download and > build something from source before he can install the EMC2 > packages. I really don't know of an appropriate solution to that. ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
